# CVE-2026-84231 — Apache Wicket

> As of 2026-11-01, CVE-2026-84231 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in Apache Wicket, CVSS v4.0 7.4. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-84231 as of 2026-11-01; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-01

## What is CVE-2026-84231?

Improper neutralization of input during web page generation in Apache Wicket. org.apache.wicket.markup.html.link.ExternalLink builds a JavaScript click handler and writes it into the tag's onclick attribute whenever the markup tag the component is bound to is not an a, link or area element. The URL held in the component's model is concatenated into a single-quoted JavaScript string literal in that handler without being escaped for that context. The same happens on the neighbouring branch, taken when popup settings are attached, where the value is concatenated into the window.open() call built by org.apache.wicket.markup.html.link.PopupSettings#getPopupJavaScript(). The only escaping applied is the markup escaping that every attribute value receives as the tag is written, which replaces an apostrophe with a character reference. A browser decodes character references in an attribute value before it compiles the event handler, so the apostrophe is restored, closes the string literal, and the rest of the model value is executed as script in the application's origin. An application is affected where it binds an ExternalLink to a markup tag that is not an anchor, such as a button or a span, and the URL in the model holds data an attacker can influence, which is the ordinary use of the component rather than a misuse of it. Nothing runs until a user activates the element. This issue affects Apache Wicket: from 8.0.0 through 8.19.0. Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. Users are recommended to upgrade to version 8.20.0, which fixes the issue.

The record classifies CVE-2026-84231 under weakness class [CWE-79](https://intel.threadlinqs.com/cwe/CWE-79). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 18 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 7.4 — High (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-01

## Is CVE-2026-84231 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Apache Software Foundation](https://intel.threadlinqs.com/vendors/apache-software-foundation): Apache Wicket

## How to fix CVE-2026-84231

Vendor advisory: [https://lists.apache.org/thread.html/39kz9838w25797bpkxn1hvfsm8jtc4zv](https://lists.apache.org/thread.html/39kz9838w25797bpkxn1hvfsm8jtc4zv). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-84231

No threat campaign in the Threadlinqs corpus currently references CVE-2026-84231, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [lists.apache.org — vendor advisory](https://lists.apache.org/thread.html/39kz9838w25797bpkxn1hvfsm8jtc4zv)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-84231
No Threadlinqs detection currently covers CVE-2026-84231; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
