WireMock Controlled Server Side Request Forgery vulnerability through URL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.6 · CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

EPSS

• CVE-2023-41327: 0.50% estimated exploitation activity in the next 30 days; percentile 42.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact WireMock can be configured to only permit proxying (and therefore recording) to certain addresses. This is achieved via a list of allowed address rules and a list of denied address rules, where the allowed list is evaluated first. Documentation. Until WireMock Webhooks Extension 3.0.0-beta-15, the filtering of target addresses from the proxy mode DID NOT work for Webhooks, so the users were potentially vulnerable regardless of the limitProxyTargets settings. Via the WireMock webhooks configuration, POST requests from a webhook might be forwarded to an arbitrary service reachable from WireMock’s instance. For example, If someone is running the WireMock docker Container inside a private cluster, they can trigger internal POST requests against unsecured APIs or even against secure ones by passing a token, discovered using another exploit, via authentication headers. Affected components - WireMock Webhooks Extension 2.x versions until 2.35.1 (security patch) - WireMock 3.x version…

Published by the source

6 Sep 2023, 20:51 UTC

Last modified by the source

6 Nov 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:16 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hq8w-9w8w-pmx7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-41327

Advisory: WireMock Controlled Server Side Request Forgery vulnerability through URL
IDs: CVE-2023-41327, GHSA-hq8w-9w8w-pmx7
Record: https://patchnext.com/advisories/cve-2023-41327 (revision 1, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.wiremock:wiremock-webhooks-extension 3.0.3, 2.35.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wiremock:wiremock-webhooks-extension: affected >= 3.0.0, < 3.0.3; >= 2.0.0, < 2.35.1; fixed in 2.35.1, 3.0.3

## Suggested inspection (read-only)
- Maven org.wiremock:wiremock-webhooks-extension: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wiremock:wiremock-webhooks-extension.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hq8w-9w8w-pmx7 (GitHub-reviewed advisory GHSA-hq8w-9w8w-pmx7 lists affected ranges: Maven org.wiremock:wiremock-webhooks-extension >=3.0.0 =2.0.0 <2.35.1)

Commands are suggestions: review each one before running it.