CVE-2023-39967

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 1.0% (63rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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

WireMock is a tool for mocking HTTP services. When certain request URLs like “@127.0.0.1:1234" are used in WireMock Studio configuration fields, the request might be forwarded to an arbitrary service reachable from WireMock’s instance. There are 3 identified potential attack vectors: via “TestRequester” functionality, webhooks and the proxy mode. As we can control HTTP Method, HTTP Headers, HTTP Data, it allows sending requests with the default level of credentials for the WireMock instance. The vendor has discontinued the affected Wiremock studio product and there will be no fix. Users are advised to find alternatives.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
1.0%
EPSS %ILE
63rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 6, 2023

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Oct 17, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Controlled and full-read SSRF through URL parameter when testing a request, webhooks and proxy mode in WireMock Studio · Advisory · wiremock/wiremock · GitHub

https://github.com/wiremock/wiremock/security/advisories/GHSA-676j-xrv3-73vc

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 87 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 13 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  2. 2026-10-23 05:36 UTCEG score recompute
  3. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  4. 2026-10-22 05:05 UTCEG score recompute
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  6. 2026-10-21 04:32 UTCEG score recompute
  7. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  8. 2026-10-20 04:01 UTCEG score recompute
  9. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  10. 2026-10-19 03:31 UTCEG score recompute
  11. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  12. 2026-10-18 03:00 UTCEG score recompute
  13. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  14. 2026-10-17 02:27 UTCEG score recompute
  15. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  16. 2026-10-16 01:55 UTCEG score recompute
  17. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  18. 2026-10-14 21:24 UTCEG score recompute
  19. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  20. 2026-10-13 17:24 UTCEG score recompute
  21. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  22. 2026-10-12 16:51 UTCEG score recompute
  23. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  24. 2026-10-11 21:47 UTCEG score recompute
  25. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
Show 62 more
  1. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  2. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  3. 2026-10-08 17:06 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  4. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  5. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  6. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  8. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-09-30 16:28 UTCEG score recompute
  11. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  15. 2026-09-26 15:56 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  17. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  20. 2026-09-18 19:25 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-09-17 19:25 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  23. 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  24. 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-09-12 14:58 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  26. 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  27. 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  28. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  29. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  30. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  31. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  32. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  33. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  34. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  35. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  36. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  37. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  38. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  39. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  40. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  41. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  42. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  43. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  44. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  45. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  46. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  47. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  48. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  49. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  50. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  51. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  52. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  53. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  54. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  55. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  56. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  57. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  58. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  59. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  60. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  61. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  62. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.8% · 53rd percentile

Frequently asked(5)

What is CVE-2023-39967?
CVE-2023-39967 is a critical-severity vulnerability; its CVE record was published on September 6, 2023. WireMock is a tool for mocking HTTP services. When certain request URLs like “@127.0.0.1:1234" are used in WireMock Studio configuration fields, the request might be forwarded to an arbitrary service reachable from WireMock’s instance. There are 3 identified potential attack vectors: via…
When was the CVE record for CVE-2023-39967 published?
The CVE record for CVE-2023-39967 was published on September 6, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-39967 actively exploited?
CVE-2023-39967 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-39967?
CVE-2023-39967 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2023-39967?
No fix for CVE-2023-39967 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-2023-39967

Explore →

Is Your Infrastructure Affected by CVE-2023-39967?

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