CVE-2013-4547

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 67.7% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Trending — 3 sources updated this weekWeaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 6 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 68%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 68%CVSS v2: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 6

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

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

across 6 countries (Australia, Bulgaria, Germany, Hong Kong, Italy)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 v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
65(Track)
EG Risk 65/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation68% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
68%
EPSS %ILE
99%
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 10× in last 7d / 27× 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-26 13:48 UTCEG score recompute▲ 7.50
  2. 2026-07-23 01:10 UTCEG score recompute▼ 6.20
  3. 2026-07-23 00:14 UTCEG score recompute▲ 6.20
  4. 2026-07-22 21:52 UTCEG score recompute▼ 9.00
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-22 09:37 UTCOSV refresh
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-20 17:03 UTCEPSS rescore
  11. 2026-07-19 02:25 UTCEPSS rescore
  12. 2026-07-16 16:58 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-13 22:26 UTCEPSS rescore
  16. 2026-07-13 06:08 UTCEPSS rescore
  17. 2026-07-12 05:42 UTCEPSS rescore
  18. 2026-07-09 19:05 UTCEPSS rescore
  19. 2026-07-08 15:10 UTCEPSS rescore
  20. 2026-07-07 13:41 UTCEPSS rescore
  21. 2026-07-05 04:51 UTCOSV refresh
  22. 2026-07-05 02:26 UTCEPSS rescore
  23. 2026-07-02 15:21 UTCEPSS rescore
  24. 2026-07-01 15:02 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEPSS rescore
Show 44 more
  1. 2026-06-29 14:02 UTCEPSS rescore
  2. 2026-06-28 14:03 UTCEPSS rescore
  3. 2026-06-27 03:05 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-18 17:49 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-17 17:49 UTCEPSS rescore
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-16 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-16 16:09 UTCOSV refresh
  18. 2026-06-15 17:44 UTCEPSS rescore
  19. 2026-06-14 23:14 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-10 22:15 UTCEPSS rescore
  23. 2026-06-10 13:18 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
  26. 2026-06-05 22:44 UTCEPSS rescore
  27. 2026-06-05 22:44 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-05 06:08 UTCEPSS rescore
  30. 2026-06-04 13:09 UTCEPSS rescore
  31. 2026-06-04 13:09 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-28 21:30 UTCEG score recompute
  35. 2026-05-28 21:30 UTCGHSA enrichment
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 13:41 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-26 07:16 UTCEPSS rescore
  42. 2026-05-21 22:39 UTCEPSS rescore
  43. 2026-05-18 21:29 UTCEPSS rescore
  44. 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 high 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 68% probability of exploitation in the next 30 days, which ranks it in the top 0.8% of all scored CVEs.
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