How severe is CVE-2013-2251?

CVE-2013-2251 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2013-2251?

Affected package information for CVE-2013-2251 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2013-2251?

Apply the apache archiva security patch or hotfix for CVE-2013-2251 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2013-2251 across my infrastructure?

Inventory every apache archiva deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2013-2251?

O3 detects and blocks CVE-2013-2251 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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

Yes. There are 7 known exploit references for CVE-2013-2251, including 2 documented proof-of-concept exploits on Exploit-DB and 5 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-2251?

CVE-2013-2251 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2013-2251 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2013-2251 (Apache Struts Improper Input Validation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2013-2251?

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

Which products and versions are affected by CVE-2013-2251?

CVE-2013-2251 affects apache archiva (2 versions, e.g. 1.2, 1.2.2); apache struts; fujitsu interstage business process manager analytics (2 versions, e.g. 12.0, 12.1); oracle siebel apps - e-billing (3 versions, e.g. 6.1, 6.1.1, 6.2). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2013-2251?

A Nuclei detection template exists for CVE-2013-2251, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2013-2251 was published on July 20, 2013 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-03-25 — agencies required to remediate by 2022-04-15

CVE-2013-2251

CRITICAL

Apache Struts 2.0.0 through 2.3.15 allows remote attackers to execute arbitrary OGNL expressions via a parameter with a crafted (1) action:, (2) redirect:, or (3) redirectAction: prefix.

Published

Jul 20, 2013

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

7 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Apache Struts 2.0.0 through 2.3.15 allows remote attackers to execute arbitrary OGNL expressions via a parameter with a crafted (1) action:, (2) redirect:, or (3) redirectAction: prefix.

Affected Products

4 products · 9 configurations

Application

archivaapache

≥ 1.3 && < 1.3.8

2 versions

1.21.2.2

Application

strutsapache

≥ 2.0.0 && ≤ 2.3.15

range

Application

interstage business process manager analyticsfujitsu

2 versions

12.012.1

Application

siebel apps - e-billingoracle

3 versions

6.16.1.16.2

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.

EDB-27135remotemultiple✓ Verified

Apache Struts 2 - DefaultActionMapper Prefixes OGNL Code Execution (Metasploit)

by Metasploit · Jul 27, 2013

Exploit-DB Source

EDB-44583webappsmultiple✓ Verified

Apache Struts2 2.0.0 < 2.3.15 - Prefixed Parameters OGNL Injection

by Takeshi Terada · Jan 14, 2014

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every apache archiva deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the apache archiva security patch or hotfix for CVE-2013-2251 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2013-2251 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2013-2251. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Apache Struts 2.0.0 through 2.3.15 allows remote attackers to execute arbitrary OGNL expressions via a parameter with a crafted (1) action:, (2) redirect:, or (3) redirectAction: prefix.

O3 Security · Runtime Protection

Is CVE-2013-2251 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2013-2251 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2013-2251

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2013-2251 being exploited in your environment?