How severe is CVE-2013-0239?

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

Which packages are affected by CVE-2013-0239?

CVE-2013-0239 affects the following packages: org.apache.cxf:cxf-rt-frontend-jaxrs (Maven), org.apache.cxf:cxf-rt-frontend-jaxrs (Maven), org.apache.cxf:cxf-rt-frontend-jaxrs (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-0239?

Update org.apache.cxf:cxf-rt-frontend-jaxrs to 2.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0239 is resolved across your whole dependency graph.

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

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

No public exploit code has been indexed for CVE-2013-0239 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-2013-0239?

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

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

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

CVE-2013-0239 was published on May 5, 2022 and was last updated on December 8, 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-0239 — cxf-rt-frontend-jaxrs

Fix: apache/cxf@e4c6b3b

CVE-2013-0239 is a Improper Authentication vulnerability in org.apache.cxf:cxf-rt-frontend-jaxrs. A fix is available for org.apache.cxf:cxf-rt-frontend-jaxrs — see the affected versions and patch details below.

Improper Authentication in Apache CXF

Published

May 5, 2022

Updated

Dec 8, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

☕org.apache.cxf:cxf-rt-frontend-jaxrs☕org.apache.cxf:cxf-rt-frontend-jaxrs☕org.apache.cxf:cxf-rt-frontend-jaxrs

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 CXF before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3, when the plaintext UsernameToken WS-SecurityPolicy is enabled, allows remote attackers to bypass authentication via a security header of a SOAP request containing a UsernameToken element that lacks a password child element.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	all versions	2.5.9`org.apache.cxf:cxf-rt-frontend-jaxrs:2.5.9`
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	≥ 2.6.0&&< 2.6.6	2.6.6`org.apache.cxf:cxf-rt-frontend-jaxrs:2.6.6`
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	≥ 2.7.0&&< 2.7.3	2.7.3`org.apache.cxf:cxf-rt-frontend-jaxrs:2.7.3`

Affected Products

1 product · 26 configurations

Application

cxfapache

≤ 2.5.8

25 versions

2.4.02.4.12.4.22.4.32.4.42.4.52.4.62.4.72.5.02.5.12.5.22.5.3

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.cxf:cxf-rt-frontend-jaxrs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf-rt-frontend-jaxrs to 2.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0239 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2013:0649
Red Hat JBoss Enterprise Application Platform 6.0	see advisory	RHSA-2013:0645
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5	`apache-cxf-0:2.4.9-6.redhat_3.ep6.el5`	RHSA-2013:0644
Red Hat JBoss Portal 6.0	see advisory	RHSA-2013:0749

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-0239 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works