How severe is CVE-2013-5960?

No CVSS score has been assigned to CVE-2013-5960 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-5960?

CVE-2013-5960 affects the following packages: org.owasp.esapi:esapi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-5960?

Update org.owasp.esapi:esapi to 2.1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5960 is resolved across your whole dependency graph.

How do I detect CVE-2013-5960 in my Maven dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-5960 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2013-5960, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-5960?

CVE-2013-5960 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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-2013-5960?

CVE-2013-5960 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-5960 published, and has it been updated?

CVE-2013-5960 was published on May 14, 2022 and was last updated on November 30, 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

CVE-2013-5960 — esapi

Fix: ESAPI/esapi-java-legacy@b7cbc53

CVE-2013-5960 is a CWE-310 vulnerability in org.owasp.esapi:esapi. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.owasp.esapi:esapi — see the affected versions and patch details below.

Missing Cryptographic Step in OWASP Enterprise Security API for Java

Published

May 14, 2022

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.owasp.esapi:esapi

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

The authenticated-encryption feature in the symmetric-encryption implementation in the OWASP Enterprise Security API (ESAPI) for Java 2.x before 2.1.0.1 does not properly resist tampering with serialized ciphertext, which makes it easier for remote attackers to bypass intended cryptographic protection mechanisms via an attack against the intended cipher mode in a non-default configuration, a different vulnerability than CVE-2013-5679.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.owasp.esapi:esapi`	≥ 2.0.0.0&&< 2.1.0.1	2.1.0.1`org.owasp.esapi:esapi:2.1.0.1`

Affected Products

1 product · 1 configurations

Application

enterprise security apiowasp

≥ 2.0 && < 2.1.0.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The authenticated-encryption feature in the symmetric-encryption impleme…

lists.owasp.orgNVDFeb 2019

Report on code.google.com

code.google.comNVDFeb 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.esapi:esapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.owasp.esapi:esapi to 2.1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5960 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-5960 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works