How severe is CVE-2013-2248?

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

Which packages are affected by CVE-2013-2248?

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

How do I fix CVE-2013-2248?

No fixed version has been published for CVE-2013-2248 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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

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

CVE-2013-2248 has an EPSS (Exploit Prediction Scoring System) score of 92.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.

What type of vulnerability is CVE-2013-2248?

CVE-2013-2248 is classified as Improper Input Validation (CWE-20). 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-2248?

CVE-2013-2248 affects apache struts (44 versions, e.g. 2.0.0, 2.0.1, 2.0.2…). Check the affected-products list on this page against your deployed version to confirm exposure.

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

A Nuclei detection template exists for CVE-2013-2248, 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-2248 published, and has it been updated?

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

CVE-2013-2248

Multiple open redirect vulnerabilities in Apache Struts 2.0.0 through 2.3.15 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in…

Published

Jul 20, 2013

Updated

Apr 29, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

92.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

Multiple open redirect vulnerabilities in Apache Struts 2.0.0 through 2.3.15 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in a parameter using the (1) redirect: or (2) redirectAction: prefix.

Affected Products

1 product · 44 configurations

Application

strutsapache

44 versions

2.0.02.0.12.0.22.0.32.0.42.0.52.0.62.0.72.0.82.0.92.0.102.0.11

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-38666remotemultiple✓ Verified

Apache Struts 2.2.3 - Multiple Open Redirections

by Takeshi Terada · Jul 16, 2013

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2248 in your stack?

O3 detects CVE-2013-2248 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works