WordPress Core 4.7.0 — 7.1.2 - Authenticated (Author+) Unauthorized Sticky Post Modification via REST API
b5541170-fd01-4d6d-934c-bfce446b3b55Published · Updated Action summary
Affected: ≤7.1.2Update to 4.7.38 or 4.8.33 or 4.9.34 or 5.0.30 or 5.1.27 or 5.2.29 or 5.3.26 or 5.4.24 or 5.5.23 or 5.6.22 or 5.7.20 or 5.8.18 or 5.9.19 or 6.0.17 or 6.1.15 or 6.2.14 or 6.3.13 or 6.4.13 or 6.5.13 or 6.6.10 or 6.7.10 or 6.8.11 or 6.9.10 or 7.0.7 or 7.1.3 or newer
Fixed versions are per release branch: update to the fix for the branch you run.
All remediation stepsOn this page3
Overview
- Advisory ID
- b5541170-fd01-4d6d-934c-bfce446b3b55
- Product
- WordPress wordpress
- Affected
- ≤7.1.2
- Fixed in
- 4.7.38, 4.8.33, 4.9.34, 5.0.30, 5.1.27, 5.2.29, 5.3.26, 5.4.24, 5.5.23, 5.6.22, 5.7.20, 5.8.18, 5.9.19, 6.0.17, 6.1.15, 6.2.14, 6.3.13, 6.4.13, 6.5.13, 6.6.10, 6.7.10, 6.8.11, 6.9.10, 7.0.7, 7.1.3
- Weakness
- CWE-863 Incorrect Authorization
- Required access
- Unknown
- Published
- · updated
- Credit
- Anthropic
- Affected≤ 7.1.2
- Patched in4.7.38 / 4.8.33 / 4.9.34 / 5.0.30 / 5.1.27 / 5.2.29 / 5.3.26 / 5.4.24 / 5.5.23 / 5.6.22 / 5.7.20 / 5.8.18 / 5.9.19 / 6.0.17 / 6.1.15 / 6.2.14 / 6.3.13 / 6.4.13 / 6.5.13 / 6.6.10 / 6.7.10 / 6.8.11 / 6.9.10 / 7.0.7 / 7.1.3
Update to 4.7.38 / 4.8.33 / 4.9.34 / 5.0.30 / 5.1.27 / 5.2.29 / 5.3.26 / 5.4.24 / 5.5.23 / 5.6.22 / 5.7.20 / 5.8.18 / 5.9.19 / 6.0.17 / 6.1.15 / 6.2.14 / 6.3.13 / 6.4.13 / 6.5.13 / 6.6.10 / 6.7.10 / 6.8.11 / 6.9.10 / 7.0.7 / 7.1.3 or newer.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
WordPress Core is vulnerable to unauthorized sticky-post modification in versions 4.7 through 7.1.2 due to an incorrect capability condition in the REST posts controller. This makes it possible for authenticated attackers, with Author-level access and above, to make posts they can edit sticky and, in affected update paths, remove sticky status without possessing the edit_others_posts capability required for sticky-post management.
Not sure which version you run? Run a passive check — it reads public files only.
Remediation & mitigations
- Update to one of the following versions, or a newer patched version: 4.7.38, 4.8.33, 4.9.34, 5.0.30, 5.1.27, 5.2.29, 5.3.26, 5.4.24, 5.5.23, 5.6.22, 5.7.20, 5.8.18, 5.9.19, 6.0.17, 6.1.15, 6.2.14, 6.3.13, 6.4.13, 6.5.13, 6.6.10, 6.7.10, 6.8.11, 6.9.10, 7.0.7, 7.1.3
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
References & provenance
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity medium, CVSS 4.3
Record last updated
Sources & licenses
- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.