LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51691: WordPress wpDiscuz Plugin <= 7.6.12 is vulnerable to Cross Site Scripting (XSS)

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51691 is a stored cross-site scripting flaw in the WordPress Comments – wpDiscuz plugin through version 7.6.12. A highly privileged user could save unsafe input that later runs in another user’s browser. Business impact is moderate: possible account misuse, content manipulation, or data exposure inside affected WordPress sites.

Executive priority

Treat as a scheduled remediation item, not an emergency, unless affected sites have many privileged contributors or handle sensitive user sessions. Prioritize external WordPress properties and high-traffic sites first.

Technical view

The issue is CWE-79 improper input neutralization during page generation in gVectors Team Comments – wpDiscuz. CVSS 3.1 is 5.9 with AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L, indicating network reachability, low attack complexity, high privileges required, user interaction, and changed scope.

Likely exposure

Exposure is limited to WordPress sites running Comments – wpDiscuz at version 7.6.12 or earlier. Risk is higher where many users have elevated WordPress privileges or where administrative sessions may view attacker-controlled comment or plugin content.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires high privileges and user interaction, reducing broad internet-scale urgency compared with unauthenticated XSS.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The bundle identifies affected versions through 7.6.12 but does not provide exploit details or a named fixed version. Avoid assuming public exploitation or specific payload behavior.

Mitigation direction

  • Inventory WordPress sites for the wpDiscuz plugin and installed version.
  • Check vendor or Patchstack guidance for a fixed release and apply it after testing.
  • Temporarily disable wpDiscuz where vulnerable versions cannot be remediated promptly.
  • Limit high-privilege WordPress accounts to trusted users only.
  • Review administrative session protections and least-privilege role assignments.

Validation and detection

  • Confirm whether Comments – wpDiscuz is installed on each WordPress site.
  • Record plugin versions and flag any deployment at 7.6.12 or earlier.
  • Review privileged WordPress users with access to wpDiscuz-managed content.
  • Check security monitoring for suspicious script-like content in plugin-managed fields.
  • Verify remediation by confirming the plugin is updated, removed, or disabled.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51691 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-51691Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gVectors TeamComments – wpDiscuzwpdiscuz, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.