WicketApplication · Apache
CVE-2015-7520
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple cross-site scripting (XSS) vulnerabilities in the (1) RadioGroup and (2) CheckBoxMultipleChoice classes in Apache Wicket 1.5.x before 1.5.15, 6.x before 6.22.0, and 7.x before 7.2.0 allow remote attackers to inject arbitrary web script or HTML via a crafted "value" attribute in a <input> element.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Wicket versions 1.5.x before 1.5.15, 6.x before 6.22.0, and 7.x before 7.2.0 contain XSS vulnerabilities in the RadioGroup and CheckBoxMultipleChoice UI components. These components fail to properly sanitize user-supplied 'value' attributes in <input> elements, allowing remote attackers to inject arbitrary JavaScript or HTML via crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WicketApplication
>= 1.5.0, < 1.5.15>= 6.0.0, < 6.22.0>= 7.0.0, < 7.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Apache Wicket library versionLocate the wicket-core JAR file or dependency declaration in your build configuration (pom.xml, build.gradle, or similar). Identify the version number from the filename or dependency version.Affected if The installed version is 1.5.0 to 1.5.14, 6.0.0 to 6.21.0, or 7.0.0 to 7.1.0.
-
Verify RadioGroup component usageSearch your codebase for imports and usage of org.apache.wicket.markup.html.form.RadioGroup. Review code that creates RadioGroup instances and processes user input.Affected if Your application uses RadioGroup to render form options with values derived from user input.
-
Verify CheckBoxMultipleChoice component usageSearch your codebase for imports and usage of org.apache.wicket.markup.html.form.CheckBoxMultipleChoice. Review code that creates CheckBoxMultipleChoice instances.Affected if Your application uses CheckBoxMultipleChoice to render form options with values derived from user input.
-
Inspect value binding to affected componentsExamine the code paths where RadioGroup or CheckBoxMultipleChoice are populated with data. Identify whether the 'value' model or property contains unsanitized user-supplied data.Affected if User-controlled data is directly assigned to the value attribute of RadioGroup or CheckBoxMultipleChoice without server-side output encoding.
Your application is affected if it runs a vulnerable Wicket version (1.5.x before 1.5.15, 6.x before 6.22.0, or 7.x before 7.2.0) AND uses RadioGroup or CheckBoxMultipleChoice with user-supplied values rendered in input elements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.5.156.22.07.2.0
Upgrade Apache Wicket to version 1.5.15, 6.22.0, or 7.2.0 or later. If immediate upgrade is not feasible, implement output encoding for all user-supplied values rendered by these components.
Fix this in Wicket
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data