Browser script execution via stored malicious content
Published Jul 31, 2025 · Updated Jul 31, 2025
Stored XSS in Alfasado PowerCMS 4.6 and earlier, 5.3 and earlier, and 6.7 and earlier allows remote authenticated users to run browser script. Public advisories do not identify the stored field or rendering path that fails to neutralize attacker-controlled content. Exploitation requires one product user to store the payload and another product user to open the malicious page; execution is confined to the victim's browser context.
Summary
What happened
Stored XSS in Alfasado PowerCMS 4.6 and earlier, 5.3 and earlier, and 6.7 and earlier allows remote authenticated users to run browser script. Public advisories do not identify the stored field or rendering path that fails to neutralize attacker-controlled content. Exploitation requires one product user to store the payload and another product user to open the malicious page; execution is confined to the victim's browser context.
The record
- CVE
- CVE-2025-41391
- Published
- Jul 31, 2025
- Updated
- Jul 31, 2025
- Vendor
- Alfasado Inc.
- Product
- PowerCMS
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2025CVE publishedPublication date reported by the CVE source.
- Jul 31, 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=4.6 and earlier (PowerCMS 4.x series)
- Affected versionversion=5.3 and earlier (PowerCMS 5.x series)
- Affected versionversion=6.7 and earlier (PowerCMS 6.x series)
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
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