How severe is CVE-2014-3526?

CVE-2014-3526 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-3526?

CVE-2014-3526 affects the following packages: org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3526?

Update org.apache.wicket:wicket-core to 1.5.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3526 is resolved across your whole dependency graph.

How do I detect CVE-2014-3526 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-3526 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2014-3526 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3526 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-3526?

CVE-2014-3526 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-3526?

CVE-2014-3526 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-3526 published, and has it been updated?

CVE-2014-3526 was published on May 13, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2014-3526 — wicket-core

HIGH

CVE-2014-3526 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.wicket:wicket-core. A fix is available for org.apache.wicket:wicket-core — see the affected versions and patch details below.

Apache Wicket Sensitive Data Exposure

Published

May 13, 2022

Updated

Feb 16, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.wicket:wicket-core`	all versions	1.5.12`org.apache.wicket:wicket-core:1.5.12`
☕Maven	`org.apache.wicket:wicket-core`	≥ 6.0&&< 6.17.0	6.17.0`org.apache.wicket:wicket-core:6.17.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 7.0.0-M1&&< 7.0.0-M3	7.0.0-M3`org.apache.wicket:wicket-core:7.0.0-M3`

Affected Products

1 product · 26 configurations

Application

wicketapache

≥ 1.5.0 && < 1.5.12

20 versions

6.0.06.1.06.1.16.2.06.3.06.4.06.5.06.6.06.7.06.8.06.9.06.9.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.wicket:wicket-core to 1.5.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3526 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3526 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 13, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2014-3526

References

Advisorynvd.nist.gov · CVE 2014 3526 Webwicket.apache.org · cve 2014 3526

Related vulnerabilities

Also affects wicket-core

This CVE is high severity; 4 of 7 other CVEs affecting wicket-core are rated as high or higher (top: high).

CVE-2026-43975CVE-2024-53299CVE-2021-23937CVE-2014-0043CVE-2016-6806CVE-2014-7808CVE-2020-11976

Same weakness: CWE-200

This CVE is high severity — higher than any of the other 1 CVE with CWE-200 (highest there: moderate).

CVE-2026-55098Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2014-3526 — wicket-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2014-3526 in your dependencies?