Stored XSS via forged settings request
Published Apr 24, 2023 · Updated Feb 4, 2025
Stored XSS in Custom Post Type and Taxonomy GUI Manager through 1.1 allows remote attackers to inject script through a forged admin request. The create-post-type settings action accepts rt_cpt_name in a POST to cptctm-create-cpt without nonce validation or sufficient sanitization, then renders it without adequate escaping. An administrator must submit the forged form; the stored script then executes in the WordPress dashboard for Contributor-level users and above.
Summary
What happened
Stored XSS in Custom Post Type and Taxonomy GUI Manager through 1.1 allows remote attackers to inject script through a forged admin request. The create-post-type settings action accepts rt_cpt_name in a POST to cptctm-create-cpt without nonce validation or sufficient sanitization, then renders it without adequate escaping. An administrator must submit the forged form; the stored script then executes in the WordPress dashboard for Contributor-level users and above.
The record
- CVE
- CVE-2023-0420
- Published
- Apr 24, 2023
- Updated
- Feb 4, 2025
- Vendor
- wpgurudev
- Product
- Custom Post Type and Taxonomy GUI Manager
- Classifications
- CWE-352, CWE-79, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan forged settings request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo