Reported vulnerability

WordPress <= 6.9.1 - Authenticated (Author+) XML External Entity Injection via getID3 Library Media Upload

Q: Which versions of WordPress are affected?

Wordfence lists these affected versions: From 6.8, through 6.8.3; From 6.9, through 6.9.1. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 6.8.4, 6.9.2. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed WordPress version?

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Published 10 Mar 2026

Updated 10 Mar 2026

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

medium · CVSS 6.5

WordPress core is vulnerable to XML External Entity (XXE) Injection via the bundled getID3 library in all versions up to and including 6.9.1. This is due to the `GETID3_LIBXML_OPTIONS` constant including the `LIBXML_NOENT` flag, which enables XML entity substitution during parsing. When WordPress processes media files containing XML metadata (specifically iXML chunks in WAV/RIFF/AVI files), the getID3 library parses the XML with entity substitution enabled, allowing local file disclosure via `file://` protocol URIs. This may make it possible for authenticated attackers with Author-level access to read arbitrary files from the server.

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

WordPress

Software: WordPress Core · wordpress
Affected versions: From 6.8, through 6.8.3; From 6.9, through 6.9.1
Fix availability: Fix available
Fixed versions: 6.8.4, 6.9.2

Recommended action

Update to one of the following versions, or a newer patched version: 6.8.4, 6.9.2

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/aa7b7474-c170-42a2-be88-0fe410a2e71b?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of WordPress are affected?

Wordfence lists these affected versions: From 6.8, through 6.8.3; From 6.9, through 6.9.1. Use the version checker above to compare your installed release with this report.

Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 6.8.4, 6.9.2. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed WordPress version?

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database