Skip to content
Noroxi
CVE-2013-0239· NVD / CVE Program· CNA redhat

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 r

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.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Mar 12, 2013
Updated
Jun 16, 2026
EPSS
4.7% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.7%

Affected systems

VendorProduct
apachecxf

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache cxfup to 2.5.8 inclusive
  • apache cxf2.4.0
  • apache cxf2.4.1
  • apache cxf2.4.2
  • apache cxf2.4.3
  • apache cxf2.4.4
  • apache cxf2.4.5
  • apache cxf2.4.6
  • apache cxf2.4.7
  • apache cxf2.5.0
  • apache cxf2.5.1
  • apache cxf2.5.2
  • apache cxf2.5.3
  • apache cxf2.5.4
  • apache cxf2.5.5
  • apache cxf2.5.6
  • apache cxf2.5.7
  • apache cxf2.6.0
  • apache cxf2.6.1
  • apache cxf2.6.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.apache.cxf:cxf-rt-frontend-jaxrsfrom 2.6.0 · before 2.6.62.6.6
Mavenorg.apache.cxf:cxf-rt-frontend-jaxrsfrom 2.7.0 · before 2.7.32.7.3
Mavenorg.apache.cxf:cxf-rt-frontend-jaxrsbefore 2.5.92.5.9
Red Hat:jboss_enterprise_application_platform:6::el5apache-cxfbefore 0:2.4.9-6.redhat_3.ep6.el50:2.4.9-6.redhat_3.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el6apache-cxfbefore 0:2.4.9-6.redhat_3.ep6.el60:2.4.9-6.redhat_3.ep6.el6

Other highest-scoring records for the same primary product.

  • CVE-2019-12419Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service.
    43Plan
  • CVE-2010-2076Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry, A
    42Plan
  • CVE-2012-2379Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1 o
    41Plan
  • CVE-2022-46364Apache CXF SSRF Vulnerability
    40Plan
  • CVE-2012-0803The WS-SP UsernameToken policy in Apache CXF 2.4.5 and 2.5.1 allows remote attackers to bypass authentication by sending an empty UsernameTo
    40Plan
  • CVE-2026-68079Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.apache.cxf:cxf-rt-frontend-jaxrs2.5.9Package registry (OSV)
Maven:org.apache.cxf:cxf-rt-frontend-jaxrs2.6.6Package registry (OSV)
Maven:org.apache.cxf:cxf-rt-frontend-jaxrs2.7.3Package registry (OSV)
red hat:apache-cxf0:2.4.9-6.redhat_3.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
P · data or configuration can be modified
Availability
none
Attack complexity
Low
Confidentiality impact
None
Integrity impact
P
Availability impact
None

CVSS vector

AV:N/AC:L/Au:N/C:N/I:P/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records