Quick answers
- Is CVE-2026-15248 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15248 being exploited in the wild.
- How severe is CVE-2026-15248?
- Medium severity, with a CVSS score of 5.5, published 2 August 2026.
- Which products and versions are affected?
- Meta Box before 5.13.1.
- Is there a fix for CVE-2026-15248?
- A patch was published on 2026-07-20: Version 5.13.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-15248 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15248?
- Check whether you run Meta Box at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (broken access control, CWE-862) in the Meta Box plugin's file deletion handler. The plugin fails to verify that a user is authorized to delete a specific attachment before processing the deletion request via the rwmb_delete_file AJAX action. An attacker with low privileges can extract a delete nonce from their own post's file field and replay it with victim attachment IDs and post IDs, bypassing WordPress's native media permissions. The attack requires Meta Box to be installed with at least one file/image field configured, and the attacker to have a user account with Contributor or higher role. The fix is available in version 5.13.1 and later.
Affected products
- Meta Meta Box before 5.13.1
Timeline
- 2026-07-20: disclosed
- 2026-07-20: patched: Version 5.13.1 released
- 2026-08-02: advisory