CVE-2026-56026

utm.codes <= 1.9.0 - Authenticated (Subscriber+) Server-Side Request Forgery

2026-06-23 00:00

Strategic Overview

Status: Patched in 1.9.1
Affected Plugin: utm.codes
Affected Version: <= 1.9.0
CVSS: 6.4Medium
Weakness type: CWE-918 · Server-Side Request Forgery (SSRF)
CVE: CVE-2026-56026

At a glance

CVE-2026-56026 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the utm.codes WordPress plugin, affecting versions <= 1.9.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.9.1; sites on affected versions should update now. Disclosed June 2026, reported by theviper17.

Vulnerability Overview

The utm.codes plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.9.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in utm.codes <= 1.9.0 takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For utm.codes the fix is 1.9.1: builds <= 1.9.0 are affected, anything from 1.9.1 onward is not.

Remediation

Update to version 1.9.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: utm.codes 1.9.1 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-56026 https://www.wordfence.com/threat-intel/vulnerabilities/id/801a48ab-f4b7-4194-a9ee-719c74e36ea2 https://nvd.nist.gov/vuln/detail/CVE-2026-56026

CVSS Vector

6.4

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/