Reflected XSS through insufficient output escaping
Published Jan 7, 2025 · Updated Apr 28, 2026
Reflected XSS in lich_wang WP-tagMaker 0.2.2 and earlier allows remote attackers to inject scripts through crafted requests. Public sources attribute the flaw to insufficient input sanitization and output escaping but do not identify the affected parameter, route, file, or function. Exploitation requires no authentication but requires a user to follow a crafted link or take an equivalent action, after which attacker-supplied script runs in that user's browser context.
Summary
What happened
Reflected XSS in lich_wang WP-tagMaker 0.2.2 and earlier allows remote attackers to inject scripts through crafted requests. Public sources attribute the flaw to insufficient input sanitization and output escaping but do not identify the affected parameter, route, file, or function. Exploitation requires no authentication but requires a user to follow a crafted link or take an equivalent action, after which attacker-supplied script runs in that user's browser context.
The record
- CVE
- CVE-2025-22338
- Published
- Jan 7, 2025
- Updated
- Apr 28, 2026
- Vendor
- lich_wang
- Product
- WP-tagMaker
- Classifications
- CWE-79, CAPEC-591, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2025CVE 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 <=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