dbcve.org
WicketApplication · Apache

CVE-2014-3526

HIGH · 7.5 CVSS v3.1 Published 2017-10-30
Fix available
A fix is available. Upgrade to 1.5.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Apache Wicket before 1.5.12, 6.x before 6.17.0, and 7.x before 7.0.0-M3 might allow remote attackers to obtain sensitive information via vectors involving identifiers for storing page markup for temporary user sessions.

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 confidence

Apache Wicket before versions 1.5.12, 6.17.0, and 7.0.0-M3 contains an information disclosure vulnerability where attackers can obtain sensitive information through identifiers used to store page markup for temporary user sessions.

MitigationUpgrade Apache Wicket to version 1.5.12 or later for the 1.5 branch, 6.17.0 or later for the 6.x branch, or 7.0.0-M3 or later for the 7.x branch.

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
Affected:>= 1.5.0, < 1.5.12= 6.0.0= 6.1.0= 6.1.1= 6.2.0= 6.3.0= 6.4.0= 6.5.0= 6.6.0= 6.7.0= 6.8.0= 6.9.0

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Wicket version
    Check your project's dependency management file (pom.xml, build.gradle, or similar) for the wicket-core artifact version, or inspect the wicket-core-*.jar file name in your lib or WEB-INF/lib directory
    Affected if The installed version falls within >= 1.5.0 and < 1.5.12, or equals any of 6.0.0 through 6.9.0
  2. Confirm page mounting is in use
    Inspect your application code for calls to mountPage(), mount(), or similar page mounting methods that store page markup in user sessions
    Affected if The application uses session-based page storage where page markup is cached using identifiers tied to user sessions
  3. Verify session store configuration
    Check your application's session configuration to confirm that page-related data is stored in the HttpSession
    Affected if Page markup or page-related objects are stored in the user session rather than being rendered dynamically on each request

You are affected if your deployed Apache Wicket version is any of 1.5.0-1.5.11, 6.0.0-6.9.0 AND your application stores page markup identifiers in user sessions for temporary state.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.5.12 or later
Fixed in 1.5.12
Interim mitigation

Upgrade Apache Wicket to version 1.5.12 or later for the 1.5 branch, 6.17.0 or later for the 6.x branch, or 7.0.0-M3 or later for the 7.x branch.

Fix this in Wicket Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3526 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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