CVE-2013-4547

NONECVSS 0.09.0▲
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 91% probability of exploitation within the next 30 days (top 0.4% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 3 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 68%
CISA-KEV: Not listedEPSS: 68%CVSS: —Exploit: NoneExposed: 3

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescaped space character in a URI.

Live · internet exposure

3 internet-exposed hosts are running an affected version of CVE-2013-4547 right now.

across 3 countries (Hong Kong, Singapore, Switzerland)top: nginx
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
—
EG Score
9.0(low)
EPSS
99.2%
KEV
Not listed

Published

November 23, 2013

Last Modified

April 29, 2026

References (18)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:41 UTCEPSS rescore
  2. 2026-07-05 04:51 UTCOSV refresh
  3. 2026-07-05 02:26 UTCEPSS rescore
  4. 2026-07-02 15:21 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-28 14:03 UTCEPSS rescore
  9. 2026-06-27 03:05 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-16 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 16:09 UTCOSV refresh
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-14 23:14 UTCEPSS rescore
Show 25 more
  1. 2026-06-13 22:57 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-10 22:15 UTCEPSS rescore
  4. 2026-06-10 13:18 UTCEPSS rescore
  5. 2026-06-08 14:14 UTCEPSS rescore
  6. 2026-06-07 15:22 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 22:44 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-05 06:08 UTCEPSS rescore
  11. 2026-06-04 13:09 UTCEPSS rescore
  12. 2026-06-04 13:09 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-31 00:14 UTCEPSS rescore
  15. 2026-05-28 21:30 UTCEG score recompute
  16. 2026-05-28 21:30 UTCGHSA enrichment
  17. 2026-05-27 13:38 UTCEPSS rescore
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 13:41 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-26 07:16 UTCEPSS rescore
  23. 2026-05-21 22:39 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcyberharsh/Nginx-CVE-2013-4547
    First seen Jun 20, 2020
    Open source ↗
  • Exploit-DBEDB-38846✓ verified
    First seen Nov 19, 2013

    Nginx 1.1.17 - URI Processing SecURIty Bypass

    Open source ↗

Frequently asked(4)

What is CVE-2013-4547?
CVE-2013-4547 is a none vulnerability published on November 23, 2013. nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescaped space character in a URI.
When was CVE-2013-4547 disclosed?
CVE-2013-4547 was first published in the National Vulnerability Database on November 23, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4547 actively exploited?
CVE-2013-4547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-4547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-4547, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-4547

Explore →

Is Your Infrastructure Affected by CVE-2013-4547?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs