Stored XSS via forged administrative request
Published Dec 16, 2024 · Updated Apr 28, 2026
CSRF in phpdevp Admin Customization 2.2 and earlier allows remote attackers to inject stored scripts through a forged request. The public CNA record and Patchstack advisory do not identify the affected handler, parameter, or missing request-validation check. Exploitation requires a privileged WordPress user to visit a crafted page, click a malicious link, or submit a forged form; the sources do not identify where the script is stored or which users later execute it.
Summary
What happened
CSRF in phpdevp Admin Customization 2.2 and earlier allows remote attackers to inject stored scripts through a forged request. The public CNA record and Patchstack advisory do not identify the affected handler, parameter, or missing request-validation check. Exploitation requires a privileged WordPress user to visit a crafted page, click a malicious link, or submit a forged form; the sources do not identify where the script is stored or which users later execute it.
The record
- CVE
- CVE-2024-54431
- Published
- Dec 16, 2024
- Updated
- Apr 28, 2026
- Vendor
- phpdevp
- Product
- Admin Customization
- Classifications
- CWE-352, CAPEC-592, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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 <=2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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