CVE-2025-11519

Image optimization service by Optimole <= 4.1.0 - Insecure Direct Object Reference to Authenticated (Author+) Media Offload

2025-10-17 18:03
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 4.1.1
Affected Plugin
Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization
Affected Version
<= 4.1.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-11519
View all Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization vulnerabilities

At a glance

CVE-2025-11519 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Optimole WordPress plugin, affecting versions <= 4.1.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 4.1.1; sites on affected versions should update now. Disclosed October 2025, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.1.0 via the /wp-json/optml/v1/move_image REST API endpoint due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to offload media that doesn't belong to them.

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 Optimole <= 4.1.0 takes an account at Author 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 Optimole the fix is 4.1.1: builds <= 4.1.0 are affected, anything from 4.1.1 onward is not.

Remediation

Update to version 4.1.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: Optimole 4.1.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-2025-11519https://www.wordfence.com/threat-intel/vulnerabilities/id/9288ed60-b14b-4188-84d4-efe770093551https://nvd.nist.gov/vuln/detail/CVE-2025-11519

Related records

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