LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47775: WordPress wpDiscuz Plugin <= 7.6.11 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team Comments — wpDiscuz plugin <= 7.6.11 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47775 is a CSRF issue in the WordPress Comments — wpDiscuz plugin through version 7.6.11. An attacker could potentially trick an authenticated site user into causing an unintended plugin-related action. The cited sources rate impact as medium with limited integrity impact, not data theft or service outage.

Executive priority

Handle this as routine but timely WordPress plugin risk. It is not described as actively exploited, but affected public WordPress sites should be inventoried and updated because CSRF can alter site state through trusted users.

Technical view

The record describes CWE-352 in gVectors Team Comments — wpDiscuz <= 7.6.11. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with the Comments — wpDiscuz plugin installed at version 7.6.11 or earlier. Sites without the plugin, or confirmed on a non-affected version, are not indicated as exposed by the provided sources.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not state active exploitation. The CVSS vector requires user interaction, consistent with CSRF, where exploitation depends on a legitimate user being induced to trigger an unwanted request.

Researcher notes

The source bundle does not identify the exact vulnerable action, patched version, nonce failure, or proof-of-concept details. Validation should stay version-based unless vendor details provide a safer authenticated test case. Avoid assuming broader impact than low integrity impact.

Mitigation direction

  • Inventory WordPress sites for the wpDiscuz plugin and installed version.
  • Treat wpDiscuz version 7.6.11 or earlier as affected.
  • Check gVectors or Patchstack guidance for the fixed version or vendor-approved mitigation.
  • Update through normal WordPress change control when a fixed release is confirmed.
  • Temporarily disable the plugin if exposure cannot be remediated promptly.

Validation and detection

  • Confirm whether Comments — wpDiscuz is installed on each WordPress site.
  • Record the exact plugin version and compare it against <= 7.6.11.
  • Review plugin changelog or vendor advisory for the CSRF fix reference.
  • Verify compensating controls do not replace the need for a vendor fix.
  • Check logs for suspicious plugin administration changes around authenticated user sessions.
Prepared
Confidence
medium
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-352: 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-47775 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
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.