Unauthenticated stored XSS via uploaded image filenames
Published Nov 6, 2023 · Updated Apr 29, 2026
Stored XSS in gVectors Team wpDiscuz 7.6.11 and earlier allows remote attackers to inject scripts through uploaded image filenames. Comment-upload filename handling stores attacker-controlled names without sufficient sanitization and later renders them without output escaping. No account is required to submit the filename, but a user must visit the affected page for the stored script to execute in that user's browser.
Summary
What happened
Stored XSS in gVectors Team wpDiscuz 7.6.11 and earlier allows remote attackers to inject scripts through uploaded image filenames. Comment-upload filename handling stores attacker-controlled names without sufficient sanitization and later renders them without output escaping. No account is required to submit the filename, but a user must visit the affected page for the stored script to execute in that user's browser.
The record
- CVE
- CVE-2023-47185
- Published
- Nov 6, 2023
- Updated
- Apr 29, 2026
- Vendor
- gVectors Team
- Product
- wpDiscuz
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2023CVE publishedPublication date reported by the CVE source.
- Apr 29, 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=n/a <=7.6.11 changes=[{"at":"7.6.12","status":"unaffected"}]
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