dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2023-45760

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 7.6.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a missing authorization vulnerability in the wpDiscuz WordPress plugin where certain functions or endpoints fail to properly validate user permissions before allowing access to sensitive operations. The vulnerability stems from incorrectly configured access control security levels that can be exploited to bypass intended authorization checks.

MitigationUpgrade wpDiscuz to the latest version (7.6.4 or higher) which contains the authorization fix. If immediate upgrade isn't possible, restrict access to vulnerable endpoints via web server configuration or disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WpdiscuzWordPress extension
Affected:< 7.6.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm wpDiscuz plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the wpdiscuz folder
    Affected if wpDiscuz plugin exists in the WordPress installation
  2. Identify installed wpDiscuz version
    Check the plugin header in wp-content/plugins/wpdiscuz/readme.txt or wpdiscuz.php for the 'Version:' field, or view the version in the WordPress plugin admin page
    Affected if The version number is below 7.6.4 (e.g., 7.6.3, 7.6.0, etc.)
  3. Verify plugin is active
    In WordPress admin, check if wpDiscuz shows as 'Active' under Plugins > Installed Plugins
    Affected if The plugin is currently active and the version is below 7.6.4
  4. Check for unauthorized access to sensitive endpoints
    Review server access logs for requests to wpDiscuz AJAX endpoints (typically /wp-admin/admin-ajax.php?action=wpdiscuz...) that originate from unauthenticated or low-privilege users accessing protected functions
    Affected if Unauthenticated or subscriber-level users can access functions that should require higher privileges (e.g., managing comments, settings, or user data)
  5. Inspect plugin capability settings
    Check wpDiscuz plugin settings under Comments > wpDiscuz > Settings > Capabilities to see if permission levels are incorrectly configured allowing low-privilege users to perform administrative actions
    Affected if Non-admin users have elevated capabilities that should not be granted

You are affected if wpDiscuz is installed, active, and running at a version lower than 7.6.4 with improperly authorized endpoint access detected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.4 or later
Fixed in 7.6.4
Interim mitigation

Upgrade wpDiscuz to the latest version (7.6.4 or higher) which contains the authorization fix. If immediate upgrade isn't possible, restrict access to vulnerable endpoints via web server configuration or disable the plugin until patched.

Recommended fix High confidence

wpDiscuz 7.6.4

  1. Backup your WordPress site before updating
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate wpDiscuz in the plugin list
  4. Update wpDiscuz to version 7.6.4 or later
  5. Verify the update was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data