Subscriber-level stored XSS via custom-field title
Published May 15, 2025 · Updated May 20, 2025
Stored XSS in WpProKing ProfilePro 1.3 and earlier allows remote authenticated users to inject scripts through a custom-field title. The profilepro_admin_add_custom_field AJAX action stores the title parameter without sanitizing or escaping it for later output. Subscriber-level access is sufficient; the script runs in an administrator's browser when the default profile's fields are edited.
Summary
What happened
Stored XSS in WpProKing ProfilePro 1.3 and earlier allows remote authenticated users to inject scripts through a custom-field title. The profilepro_admin_add_custom_field AJAX action stores the title parameter without sanitizing or escaping it for later output. Subscriber-level access is sufficient; the script runs in an administrator's browser when the default profile's fields are edited.
The record
- CVE
- CVE-2024-6668
- Published
- May 15, 2025
- Updated
- May 20, 2025
- Vendor
- WpProKing
- Product
- ProfilePro
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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.3
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 subscriber custom-field stored-XSS 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