dbcve.org
StudioApplication · Wiremock

CVE-2023-39967

CRITICAL · 10.0 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 2.32.0-17 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WireMock Studio contains a Server-Side Request Forgery (SSRF) vulnerability where specific URL patterns like '@127.0.0.1:1234' in configuration fields allow requests to be forwarded to arbitrary internal services reachable from the WireMock instance. Attackers can exploit this through three vectors (TestRequester, webhooks, and proxy mode) with control over HTTP method, headers, and data, using the application's default credentials.

MitigationSince the vendor has discontinued WireMock Studio with no fix planned, users must immediately migrate to alternative solutions - this critical SSRF vulnerability with CVSS 10 requires urgent remediation through complete product replacement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StudioApplication
Affected:<= 2.32.0-17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WireMock Studio installation and version
    Locate the WireMock Studio installation and check the version. If using Docker, run 'docker ps' and inspect the image tag. If installed as a JAR, check the filename or run 'java -jar wiremock-studio.jar --version' if supported.
    Affected if The installed version is 2.32.0-17 or lower
  2. Determine if TestRequester extension is enabled
    Inspect the WireMock Studio configuration files (typically in /config or as startup parameters) for 'test-requester' or 'TestRequester' extension loading. Check the extensions or plugins configuration section.
    Affected if TestRequester extension is loaded and accessible via the API endpoint /__admin/testrequester
  3. Check webhook configuration exposure
    Review WireMock Studio's webhook settings accessible via the admin API at /__admin/webhooks or through the web interface settings panel.
    Affected if Webhook functionality is accessible and configurable through the WireMock Studio interface
  4. Verify proxy mode configuration
    Check WireMock Studio proxy settings through the admin API endpoint /__admin/proxy or through the web interface under Proxy settings.
    Affected if Proxy mode is enabled, allowing forwarding of requests to arbitrary URLs
  5. Inspect for suspicious internal access patterns in logs
    Review WireMock Studio request logs (available via /__admin/requests or log files) for requests containing '@127.0.0.1:' or '@localhost:' URL patterns, or requests targeting internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x).

You are affected if WireMock Studio version 2.32.0-17 or lower is running with TestRequester, webhooks, or proxy mode enabled, as any of these vectors can be exploited to perform SSRF attacks against internal services.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.32.0-17
Interim mitigation

Since the vendor has discontinued WireMock Studio with no fix planned, users must immediately migrate to alternative solutions - this critical SSRF vulnerability with CVSS 10 requires urgent remediation through complete product replacement.

Recommended fix High confidence
  1. 1. Acknowledge that WireMock Studio (version <= 2.32.0-17) is discontinued and will not receive security patches.
  2. 2. Migrate to an alternative solution such as: standard WireMock (wiremock.org), Mockoon, Postman Mock Servers, or another actively maintained API mocking tool.
  3. 3. If continuing to use WireMock Studio temporarily is unavoidable, implement network segmentation to restrict the instance from accessing sensitive internal services.
  4. 4. Implement firewall rules to block outbound connections from the WireMock Studio server to internal network ranges.
  5. 5. Remove any WireMock Studio instances exposed to untrusted networks immediately.
Caveat WireMock Studio is discontinued with no successor product; migration to an alternative mocking solution is required.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Studio Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39967 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data