LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46309: WordPress wpDiscuz plugin <= 7.6.10 - 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.10.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-46309 is a medium-severity access-control issue in the WordPress wpDiscuz plugin through version 7.6.10. An unauthenticated attacker may be able to make a limited unauthorized change. The available sources do not show active exploitation or provide detailed remediation text.

Executive priority

Treat this as a routine but timely WordPress plugin remediation item. It does not carry critical impact or confirmed exploitation in the provided sources, but public unauthenticated reachability makes internet-facing affected sites worth prioritizing in normal patch cycles.

Technical view

The CVE describes missing authorization in AdvancedCoding wpDiscuz through 7.6.10, mapped to CWE-862. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and no user interaction required. Impact is limited to integrity; confidentiality and availability are not rated as affected.

Likely exposure

Exposure is most likely on public WordPress sites running wpDiscuz version 7.6.10 or earlier. Sites without the plugin, or with versions confirmed outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates unauthenticated network reachability with low attack complexity. However, the provided bundle marks CISA KEV as false and contains no cited evidence of active exploitation, public exploit use, or exploitation at scale.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack advisory reference. The bundle does not include exploit details, a named fixed version, or precise affected actions. Validation should focus on plugin presence, version, and vendor advisory confirmation rather than speculative behavior.

Mitigation direction

  • Check AdvancedCoding or Patchstack guidance for the official fixed version or remediation.
  • Update wpDiscuz using a vendor-supported release path once remediation is confirmed.
  • Disable or remove the plugin where it is not business-critical and remains affected.
  • Do not rely on unverified workarounds not documented by the vendor or advisory.

Validation and detection

  • Inventory WordPress sites for wpDiscuz and record exact plugin versions.
  • Flag any wpDiscuz installation at version 7.6.10 or earlier for remediation review.
  • Confirm whether vendor guidance identifies a fixed version before closing the finding.
  • Review site logs for unexplained unauthenticated changes involving wpDiscuz functionality.
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-46309 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

CWE details

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