Stored script execution via crafted comments
Published Dec 8, 2022 · Updated Apr 15, 2025
Stored cross-site scripting in LinZhaoguan pb-cms 2.0 allows remote attackers to run script in a visitor's browser through comments. The public record identifies the /blog/comment Message Board endpoint but does not disclose the affected parameter or encoding failure. A victim must view the malicious comment; script execution is limited to the victim's pb-cms browser context.
Summary
What happened
Stored cross-site scripting in LinZhaoguan pb-cms 2.0 allows remote attackers to run script in a visitor's browser through comments. The public record identifies the /blog/comment Message Board endpoint but does not disclose the affected parameter or encoding failure. A victim must view the malicious comment; script execution is limited to the victim's pb-cms browser context.
The record
- CVE
- CVE-2022-4354
- Published
- Dec 8, 2022
- Updated
- Apr 15, 2025
- Vendor
- LinZhaoguan
- Product
- pb-cms
- Classifications
- CWE-79, CWE-707, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=2.0
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
- Gitee issue proof of conceptproof of concept · unverified
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