LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45760: WordPress wpDiscuz plugin <= 7.6.3 - Broken Access Control vulnerability

Missing Authorization vulnerability in AdvancedCoding wpDiscuz wpdiscuz allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects wpDiscuz: from n/a through <= 7.6.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the WordPress wpDiscuz plugin through version 7.6.3. A logged-in attacker may access information they should not because authorization checks are missing. The business impact appears limited to confidentiality, not data modification or outage, based on the provided CVSS vector.

Executive priority

Handle in the normal vulnerability management cycle unless the plugin is widely deployed on sensitive sites. Escalate priority where many users can authenticate or where comments expose sensitive workflows or private content.

Technical view

CVE-2023-45760 is a CWE-862 missing authorization flaw in AdvancedCoding wpDiscuz. The source bundle describes broken access control through version 7.6.3 with CVSS 3.1 score 4.3: network reachable, low complexity, low privileges required, no user interaction, and low confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites running wpDiscuz version 7.6.3 or earlier. Because privileges are required, anonymous internet traffic is not enough according to the supplied CVSS vector. The bundle does not identify affected configurations beyond the plugin and version range.

Exploitation context

The source bundle does not support active exploitation. CISA KEV status is false, and no cited source claims exploitation in the wild. Treat this as a reachable authenticated access-control issue until vendor details clarify the affected functionality.

Researcher notes

Evidence is incomplete. The description states wpDiscuz through 7.6.3 is affected, but the affected metadata is sparse and lists defaultStatus as unaffected. No patched version, vulnerable endpoint, or workaround is provided in the bundle, so validation should focus on inventory, versioning, and vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for wpDiscuz installations and versions.
  • Prioritize remediation for wpDiscuz 7.6.3 or earlier.
  • Check vendor and Patchstack guidance for the confirmed fixed version.
  • Apply the vendor-supported update or mitigation when identified.
  • Restrict unnecessary WordPress accounts while remediation is pending.

Validation and detection

  • Confirm whether wpDiscuz is installed on each WordPress site.
  • Record the exact wpDiscuz version from the WordPress plugin inventory.
  • Flag versions 7.6.3 or earlier for remediation tracking.
  • Review site logs for unusual authenticated access patterns.
  • Verify remediation against vendor or Patchstack release guidance.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-45760 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:L/UI:N/S:U/C:L/I:N/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:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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
AdvancedCodingwpDiscuzwpdiscuz, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.