TaxoPress <= 3.50.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Private Post Disclosure
Strategic Overview
- Status
- Patched in 3.51.0
- Affected Version
<= 3.50.0- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-15231
At a glance
CVE-2026-15231 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Tag, Category, and Taxonomy Manager WordPress plugin, affecting versions <= 3.50.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.51.0; sites on affected versions should update now. Disclosed July 2026, reported by Duy Tran.
Vulnerability Overview
The TaxoPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.50.0. This is due to missing authorization check on a user-supplied post ID passed to get_post() in the AI preview AJAX handler, allowing any authenticated user to retrieve post data regardless of post status or ownership. This makes it possible for authenticated attackers, with contributor-level access and above, to read the content of private or draft posts belonging to other users by supplying an arbitrary post ID.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Tag, Category, and Taxonomy Manager <= 3.50.0 carries this weakness at get_post(), and reaching it takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Tag, Category, and Taxonomy Manager the fix is 3.51.0: builds <= 3.50.0 are affected, anything from 3.51.0 onward is not.
Remediation
Update to version 3.51.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Tag, Category, and Taxonomy Manager 3.51.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Tag, Category, and Taxonomy Manager – Autotagger Automatically Add Terms
- 6.5CVE-2025-13922: Tag, Category, and Taxonomy Manager SQL Injection
CVE-2025-13922 - 6.5CVE-2025-13359: Tag, Category, and Taxonomy Manager SQL Injection
CVE-2025-13359 - 6.4CVE-2024-2830: WordPress Tag and Category Manager Stored XSS
CVE-2024-2830 - 6.1TaxoPress <= 3.4.4 Reflected Cross-Site Scripting
- 5.5CVE-2023-2168: TaxoPress <= 3.6.4 Stored Cross-Site Scripting
CVE-2023-2168 - 5.5CVE-2023-2169: TaxoPress <= 3.6.4 Stored Cross-Site Scripting
CVE-2023-2169 - 5.5CVE-2023-2170: TaxoPress <= 3.6.4 Stored Cross-Site Scripting
CVE-2023-2170 - 5.5CVE-2021-24444: TaxoPress <= 3.0.7.1 Stored Cross-Site Scripting
CVE-2021-24444
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C