Microsoft Azure Storage for WordPress <= 4.5.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Media Deletion
Strategic Overview
- Status
- Patched in 4.5.2
- Affected Plugin
- Microsoft Azure Storage for WordPress
- Affected Version
<= 4.5.1- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-10749
At a glance
CVE-2025-10749 is a medium-severity Missing Authorization vulnerability in the Microsoft Azure Storage for WordPress WordPress plugin, affecting versions <= 4.5.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.5.2; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The Microsoft Azure Storage for WordPress plugin for WordPress is vulnerable to Unauthorized Arbitrary Media Deletion in all versions up to, and including, 4.5.1. This is due to missing capability checks on the 'azure-storage-media-replace' AJAX action. This makes it possible for authenticated attackers with subscriber-level access and above to delete arbitrary media files from the WordPress Media Library via the replace_attachment parameter granted they can access the nonce which is exposed to all authenticated users.
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-862: Missing Authorization
Microsoft Azure Storage for WordPress <= 4.5.1 carries this weakness at azure-storage-media-replace, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Microsoft Azure Storage for WordPress the fix is 4.5.2: builds <= 4.5.1 are affected, anything from 4.5.2 onward is not.
Remediation
Update to version 4.5.2, 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: Microsoft Azure Storage for WordPress 4.5.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C