Which products and versions are affected by CVE-2025-14675?

Affected: wpmetabox/meta-box (composer); Meta Box (wordpress-plugin). The full list is in the CVE brief.

Is CVE-2025-14675 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2025-14675 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2025-14675?

No public exploit code is known.

Is there a fix for CVE-2025-14675?

Fixed versions are available, including Meta Box 5.11.2, wpmetabox/meta-box 5.11.2.

How urgently should CVE-2025-14675 be patched?

Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Request A Demo

Vulnerability Intelligence

CVE-2025-14675

High

Meta Box Plugin for WordPress: Authenticated (Contributor+) Arbitrary File Deletion via ajax_delete_file

Published Mar 7, 2026 · Updated Aug 12, 2026 · Also known as 036467de-95bb-4bfd-9522-df8dc17f3102, GHSA-m4q3-832v-44j6

Key Facts

Patch in the next maintenance window

CVE-2025-14675 is a high-severity vulnerability (CVSS 7.2 v3.1) affecting wpmetabox/meta-box (composer), Meta Box (wordpress-plugin).
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 2.4% probability of exploitation in the next 30 days.
Fixed versions are available, including Meta Box 5.11.2, wpmetabox/meta-box 5.11.2.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

CVSS v3.1

7.2

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

EPSS (30-day exploit likelihood)

2.4%

Higher than 83.6% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2025-14675 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

The Meta Box plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'ajax_delete_file' function in all versions up to, and including, 5.11.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

Affected Products

3 affected entries in total

Product	Affected versions	Fixed in
wpmetabox/meta-boxcomposer	See advisory	5.11.2
Meta Boxwordpress-plugin	See advisory	5.11.2

Patched Releases

Meta Box

5.11.2

wpmetabox/meta-box

5.11.2

Timeline

Publicly disclosed
Mar 7, 2026
Last updated
Aug 12, 2026

Weakness Type

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

References

7 more references in the full CVE brief

FAQ

Common Questions.

The Meta Box plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'ajax_delete_file' function in all versions up to, and including, 5.11.1.
Affected: wpmetabox/meta-box (composer); Meta Box (wordpress-plugin). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Meta Box 5.11.2, wpmetabox/meta-box 5.11.2.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Is CVE-2025-14675 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.