Reported vulnerability

WordPress Core <= 7.1 - Authenticated (Contributor+) Insecure Direct Object Reference to Arbitrary Post Overwrite

Q: Which versions of WordPress are affected?

Wordfence lists these affected versions: Start version unspecified, through 6.6.7; From 6.7, through 6.7.7; From 6.8, through 6.8.8; From 6.9, through 6.9.7; From 7.0, through 7.0.4; From 7.1, through 7.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.6.8, 6.7.8, 6.8.9, 6.9.8, 7.0.5, 7.1.1. 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 17 Sept 2026

Updated 17 Sept 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 4.3

WordPress Core is vulnerable to Insecure Direct Object Reference via the _wp_translate_postdata() function in various versions up to, and including, 7.1 due to the create path (no post_ID) honoring a raw 'ID' parameter, which wp_insert_post() then treats as an update - bypassing the per-post edit_post capability checks that only run on the update path. This makes it possible for authenticated attackers with Contributor-level access and above to overwrite the content of arbitrary existing posts, including posts authored by higher-privileged users.

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

WordPress

Software: WordPress Core · wordpress
Affected versions: Start version unspecified, through 6.6.7; From 6.7, through 6.7.7; From 6.8, through 6.8.8; From 6.9, through 6.9.7; From 7.0, through 7.0.4; From 7.1, through 7.1
Fix availability: Fix available
Fixed versions: 6.6.8, 6.7.8, 6.8.9, 6.9.8, 7.0.5, 7.1.1

Recommended action

Update to one of the following versions, or a newer patched version: 6.6.8, 6.7.8, 6.8.9, 6.9.8, 7.0.5, 7.1.1

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/adc90b32-f973-4c8e-b419-0614d4642b7f?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: Start version unspecified, through 6.6.7; From 6.7, through 6.7.7; From 6.8, through 6.8.8; From 6.9, through 6.9.7; From 7.0, through 7.0.4; From 7.1, through 7.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.6.8, 6.7.8, 6.8.9, 6.9.8, 7.0.5, 7.1.1. 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