How to check if you are exposed to CVE-2013-2251
- Find every Apache Struts system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2013-2251.
US federal agencies had to fix this by 2022-04-15. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Timeline
- · Added to CISA's Known Exploited Vulnerabilities catalog
- · Fix-by date for US federal agencies, passed 1,661 days ago
Weakness type
More exploited Apache vulnerabilities
CISA lists 41 exploited Apache vulnerabilities. The closest matches:
- CVE-2016-3081Apache Struts Command Injection VulnerabilityAdded 2026-10-08
- CVE-2020-17530Apache Struts Remote Code Execution VulnerabilityAdded 2021-11-03
- CVE-2018-11776Apache Struts Remote Code Execution VulnerabilityAdded 2021-11-03
- CVE-2017-9805Apache Struts Deserialization of Untrusted Data VulnerabilityAdded 2021-11-03
- CVE-2017-5638Apache Struts Remote Code Execution VulnerabilityAdded 2021-11-03
- CVE-2026-34486Apache Tomcat Missing Encryption of Sensitive Data VulnerabilityAdded 2026-08-04
- CVE-2026-34197Apache ActiveMQ Improper Input Validation VulnerabilityAdded 2026-04-16
- CVE-2024-38475Apache HTTP Server Improper Escaping of Output VulnerabilityAdded 2025-05-01
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.