CVE-2026-94672

Safe SVG <= 2.5.0 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-09-23 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 2.5.1
Affected Plugin
Safe SVG
Affected Version
<= 2.5.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-94672
View all Safe SVG vulnerabilities

At a glance

CVE-2026-94672 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Safe SVG WordPress plugin, affecting versions <= 2.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.5.1; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Safe SVG plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.5.0. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Safe SVG <= 2.5.0 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Safe SVG the fix is 2.5.1: builds <= 2.5.0 are affected, anything from 2.5.1 onward is not.

Remediation

Update to version 2.5.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Safe SVG 2.5.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-94672https://www.wordfence.com/threat-intel/vulnerabilities/id/6dd5a799-9df8-4d58-b972-8ec7153a0e65https://nvd.nist.gov/vuln/detail/CVE-2026-94672

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C