dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2024-35681

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 7.6.19 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in gVectors Team wpDiscuz allows Stored XSS.This issue affects wpDiscuz: from n/a through 7.6.18.

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 · high confidence

Stored XSS vulnerability in wpDiscuz plugin allows injection of malicious scripts through user input that is not properly sanitized before being rendered in web pages. The vulnerability stems from improper neutralization of input during web page generation, allowing attackers to embed malicious JavaScript code in comments that will execute when viewed by other users.

MitigationUpgrade wpDiscuz to the latest version (7.6.19 or later) which includes proper input sanitization and output encoding. If immediate upgrade is not possible, implement web application firewall rules to detect and block XSS payloads in comment submissions.

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.19

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Locate wpDiscuz plugin installation
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'wpDiscuz' or 'Gvectors wpdiscuz' in the list.
    Affected if wpDiscuz is not found in the installed plugins list
  2. Identify installed wpDiscuz version
    In the Plugins list, locate the wpDiscuz entry and note the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and check the main plugin file (usually wpdiscuz.php or class-wpdiscuz.php) for the 'Version' header comment.
    Affected if The installed version is any version lower than 7.6.19 (e.g., 7.6.18, 7.6.17, 7.5.x, etc.)
  3. Verify comment system is active
    In WordPress admin, go to Settings > Discussion and confirm that 'Allow people to submit comments on new posts' is checked, or check that comments are enabled on specific posts/pages where wpDiscuz is loaded.
    Affected if Comments are enabled and publicly accessible, allowing user-submitted content to be stored and displayed
  4. Inspect comment submission for sanitization gaps
    Submit a test comment containing a benign XSS probe such as <script>alert('test')</script> or <img src=x onerror=alert('test')> on a public post, then view the comment as a logged-out visitor to see if the raw script tags render unescaped.
    Affected if The script tags or event handler attributes appear literally in the rendered HTML without being encoded or stripped

You are affected if wpDiscuz is installed with a version lower than 7.6.19 AND the comment feature is enabled, allowing unsanitized script tags to execute when comments are viewed.

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.19 or later
Fixed in 7.6.19
Interim mitigation

Upgrade wpDiscuz to the latest version (7.6.19 or later) which includes proper input sanitization and output encoding. If immediate upgrade is not possible, implement web application firewall rules to detect and block XSS payloads in comment submissions.

Recommended fix High confidence

wpDiscuz version 7.6.19

  1. 1. Create a full backup of your WordPress site (database and files) before performing any updates.
  2. 2. Navigate to your WordPress admin dashboard > Plugins page.
  3. 3. Find the wpDiscuz plugin in the installed plugins list.
  4. 4. Click the 'Update now' link if an update is available, or use WordPress automatic update feature.
  5. 5. Verify the plugin has been updated to version 7.6.19 or later.
  6. 6. Test the comment submission functionality to ensure the plugin is working correctly after the update.

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35681 — 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-2024-35681 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