CVE-2023-51691 WordPress wpDiscuz Plugin <= 7.6.12 is vulnerable to Cross Site Scripting (XSS)
Stored XSS in wpDiscuz allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2023-51691?
CVE-2023-51691 is a medium-severity cross-site scripting vulnerability in gVectors Team Comments – wpDiscuz, published on 1 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in gVectors Team Comments – wpDiscuz allows Stored XSS.This issue affects Comments – wpDiscuz: from n/a through 7.6.12.
Weakness: CWE-79
Which versions are affected by CVE-2023-51691?
It affects 1 product.
Products include Gvectors Wpdiscuz.
How do I fix CVE-2023-51691?
No fix has been published for CVE-2023-51691 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2023-51691 being exploited?
There is no known exploitation of CVE-2023-51691 in the wild and no public exploit code.
Other vulnerabilities in gVectors Team Comments – wpDiscuz
- CVE-2020-24186 File upload in n/a
- CVE-2024-9488 Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider
- CVE-2020-13640 SQL injection in n/a
- CVE-2026-22193 wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions()
- CVE-2026-22192 Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage
Sources
Also known as GHSA-66qc-rgfw-8hq2.