CVE-2010-2263

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (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:N/A:N. 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 71.9% 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
Weaponized
5.0EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • 2 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 72%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 72%CVSS v2: 5.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: 2

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

nginx 0.8 before 0.8.40 and 0.7 before 0.7.66, when running on Windows, allows remote attackers to obtain source code or unparsed content of arbitrary files under the web document root by appending ::$DATA to the URI.

Internet exposure · derived from Shodan data

2 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2010-2263, in our KEV-Exposure radar’s Shodan-derived sample.

across 2 countries (Saudi Arabia, United States)top: nginx
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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
Severity50% × 45%
Exploitation72% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
72%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 15, 2010

Last Modified

April 29, 2026

References (8)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 11× 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-10-05 17:37 UTCEPSS rescore
  2. 2026-10-03 14:20 UTCEPSS rescore
  3. 2026-09-29 08:06 UTCEG score recompute
  4. 2026-09-26 15:52 UTCEPSS rescore
  5. 2026-09-24 13:57 UTCEPSS rescore
  6. 2026-09-20 20:08 UTCEPSS rescore
  7. 2026-09-16 13:58 UTCEPSS rescore
  8. 2026-09-13 16:40 UTCEPSS rescore
  9. 2026-09-12 14:54 UTCEPSS rescore
  10. 2026-09-10 09:24 UTCEPSS rescore
  11. 2026-09-06 13:41 UTCEPSS rescore
  12. 2026-09-05 15:22 UTCEPSS rescore
  13. 2026-09-04 13:55 UTCEPSS rescore
  14. 2026-08-28 21:34 UTCEPSS rescore
  15. 2026-08-26 14:40 UTCEPSS rescore
  16. 2026-08-25 13:43 UTCEPSS rescore
  17. 2026-08-19 16:58 UTCEPSS rescore
  18. 2026-08-16 02:09 UTCEPSS rescore
  19. 2026-08-15 01:25 UTCEPSS rescore
  20. 2026-08-07 16:21 UTCEPSS rescore
  21. 2026-08-05 19:11 UTCEPSS rescore
  22. 2026-08-04 15:04 UTCEPSS rescore
  23. 2026-08-01 04:10 UTCEPSS rescore
  24. 2026-07-30 01:26 UTCEPSS rescore
  25. 2026-07-26 13:41 UTCEG score recompute▲ 5.00
Show 70 more
  1. 2026-07-23 01:02 UTCEG score recompute
  2. 2026-07-23 00:38 UTCEG score recompute▼ 7.30
  3. 2026-07-23 00:06 UTCEG score recompute▲ 7.30
  4. 2026-07-22 21:45 UTCEG score recompute
  5. 2026-07-22 14:03 UTCEPSS rescore
  6. 2026-07-22 14:03 UTCEPSS rescore
  7. 2026-07-21 15:20 UTCEPSS rescore
  8. 2026-07-20 17:03 UTCEPSS rescore
  9. 2026-07-19 02:25 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-13 22:25 UTCEPSS rescore
  14. 2026-07-13 06:08 UTCEPSS rescore
  15. 2026-07-11 08:22 UTCEPSS rescore
  16. 2026-07-05 02:26 UTCEPSS rescore
  17. 2026-07-02 14:01 UTCEPSS rescore
  18. 2026-06-29 14:02 UTCEPSS rescore
  19. 2026-06-29 14:02 UTCEPSS rescore
  20. 2026-06-28 14:03 UTCEPSS rescore
  21. 2026-06-27 03:05 UTCEPSS rescore
  22. 2026-06-25 13:46 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-23 21:29 UTCEPSS rescore
  25. 2026-06-21 14:53 UTCEPSS rescore
  26. 2026-06-21 01:56 UTCEPSS rescore
  27. 2026-06-21 01:56 UTCEPSS rescore
  28. 2026-06-18 17:49 UTCEPSS rescore
  29. 2026-06-18 17:49 UTCEPSS rescore
  30. 2026-06-17 17:49 UTCEPSS rescore
  31. 2026-06-17 17:49 UTCEPSS rescore
  32. 2026-06-15 17:44 UTCEPSS rescore
  33. 2026-06-12 23:08 UTCEPSS rescore
  34. 2026-06-12 23:08 UTCEPSS rescore
  35. 2026-06-11 13:56 UTCEPSS rescore
  36. 2026-06-10 22:14 UTCEPSS rescore
  37. 2026-06-10 13:17 UTCEPSS rescore
  38. 2026-06-08 14:13 UTCEPSS rescore
  39. 2026-06-07 15:22 UTCEPSS rescore
  40. 2026-06-07 15:22 UTCEPSS rescore
  41. 2026-06-06 13:44 UTCEPSS rescore
  42. 2026-06-06 13:44 UTCEPSS rescore
  43. 2026-06-05 22:44 UTCEPSS rescore
  44. 2026-06-05 22:44 UTCEPSS rescore
  45. 2026-06-05 06:07 UTCEPSS rescore
  46. 2026-06-05 06:07 UTCEPSS rescore
  47. 2026-06-04 13:09 UTCEPSS rescore
  48. 2026-06-04 13:09 UTCEPSS rescore
  49. 2026-06-02 20:10 UTCEPSS rescore
  50. 2026-06-02 20:10 UTCEPSS rescore
  51. 2026-05-31 22:28 UTCEPSS rescore
  52. 2026-05-31 22:28 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-31 00:13 UTCEPSS rescore
  55. 2026-05-29 13:40 UTCEPSS rescore
  56. 2026-05-29 11:18 UTCEG score recompute
  57. 2026-05-29 11:18 UTCGHSA enrichment
  58. 2026-05-28 13:42 UTCEPSS rescore
  59. 2026-05-28 13:42 UTCEPSS rescore
  60. 2026-05-26 07:16 UTCEPSS rescore
  61. 2026-05-26 07:16 UTCEPSS rescore
  62. 2026-05-22 21:15 UTCEPSS rescore
  63. 2026-05-22 21:15 UTCEPSS rescore
  64. 2026-05-22 21:15 UTCEPSS rescore
  65. 2026-05-21 22:39 UTCEPSS rescore
  66. 2026-05-20 22:37 UTCEPSS rescore
  67. 2026-05-20 22:37 UTCEPSS rescore
  68. 2026-05-20 22:37 UTCEPSS rescore
  69. 2026-05-18 21:29 UTCEPSS rescore
  70. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-13818✓ verified
    First seen Jun 11, 2010

    Nginx 0.8.36 - Source Disclosure / Denial of Service

    Open source ↗
  • Exploit-DBEDB-13822✓ verified
    First seen Jun 11, 2010

    Nginx 0.7.65/0.8.39 (dev) - Source Disclosure / Download

    Open source ↗
  • Metasploitauxiliary/scanner/http/nginx_source_disclosure✓ verified
    First seen Jan 1, 2010

    Nginx Source Code Disclosure/Download

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2010-2263?
CVE-2010-2263 is a medium vulnerability published on June 15, 2010. nginx 0.8 before 0.8.40 and 0.7 before 0.7.66, when running on Windows, allows remote attackers to obtain source code or unparsed content of arbitrary files under the web document root by appending ::$DATA to the URI.
When was CVE-2010-2263 disclosed?
CVE-2010-2263 was first published on June 15, 2010, 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-2010-2263 actively exploited?
CVE-2010-2263 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 72% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2010-2263?
No fix for CVE-2010-2263 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2010-2263

Explore →

Is Your Infrastructure Affected by CVE-2010-2263?

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

Book a Demo →Browse All CVEs