SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-76984

MEDIUM · CVSS 5.4 EPSS 0.50%

Source: NVD + CISA KEV + EPSS · Published 2026-08-31 · Last synced 2026-09-07

CyberRota Analysis

AI-Generated

Apache Wicket is vulnerable due to improper handling of input during web page generation, specifically in the construction of `<meta>` and `<link>` tags, which can lead to injection of unintended attributes. This vulnerability allows attackers to manipulate attribute values, potentially leading to cross-site scripting (XSS) or other injection attacks. Organizations using affected versions (8.0.0 to 8.18.0, 9.0.0 to 9.23.0, and 10.0.0 to 10.10.0) should prioritize upgrading to the patched versions (8.19.0, 9.24.0, or 10.11.0) to mitigate the risk.

CVE
CVE-2026-76984
Severity
MEDIUM
CVSS
5.4
EPSS
0.50%
Apache

Original NVD Description

Improper neutralization of input during web page generation in Apache Wicket. org.apache.wicket.markup.head.MetaDataHeaderItem generates <meta> and <link> header tags. It escaped the attribute names it wrote, but ran the attribute values through a replacement of " with \". A backslash before a double quote means nothing in HTML, so a value containing a double quote ends its own attribute and what follows is parsed as further attributes of the generated tag. An application is affected where it supplies an attribute value holding data an attacker can influence, through addTagAttribute or the forMetaTag and forLinkTag factory methods. A value may be given as an IModel, so it is not necessarily a literal. There is no setting to change; an application can only avoid supplying a value that contains a double quote. Note that these values have never been escaped effectively: before the change released in 6.24.0, 7.4.0 and 8.0.0 they were written with no escaping at all. This issue affects Apache Wicket: from 8.0.0 through 8.18.0, from 9.0.0 through 9.23.0, from 10.0.0 through 10.10.0. Older, unsupported releases from 6.17.0 onwards are also affected. Users are recommended to upgrade to version 8.19.0, 9.24.0 or 10.11.0, which fix the issue.

Related CVEs

Other vulnerabilities affecting the same vendor(s)