dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22215

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 7.6.47 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability in the getFollowsPage() function that allows attackers to trigger unauthorized actions without nonce validation. Attackers can craft malicious requests to enumerate follow relationships and manipulate user follow data by exploiting the missing CSRF protection in the follows page handler.

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

wpDiscuz before 7.6.47 has a CSRF vulnerability in the getFollowsPage() function where missing nonce validation allows attackers to craft malicious requests that can enumerate follow relationships and manipulate user follow data without the victim's consent.

MitigationUpdate wpDiscuz to version 7.6.47 or later, which implements proper nonce validation for the getFollowsPage() function to prevent CSRF attacks.

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

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Verify wpDiscuz plugin is installed
    Check your WordPress plugins directory or navigate to WP Admin > Plugins to confirm wpDiscuz is installed and active
    Affected if wpDiscuz is installed and active in the WordPress environment
  2. Determine installed wpDiscuz version
    In WordPress admin, go to Plugins > wpDiscuz > view the version number displayed, or check the plugin header in wp-content/plugins/wpdiscuz/wpdiscuz.php for the 'Version' constant
    Affected if The installed version is lower than 7.6.47 (e.g., 7.6.46, 7.6.45, etc.)
  3. Identify the vulnerable endpoint
    Inspect AJAX requests made when accessing user follow functionality. The vulnerable endpoint is the AJAX action handling getFollowsPage() - typically found in wpdiscuz/classes/class.WpdiscuzCore.php or related AJAX handler files
    Affected if The getFollowsPage() function handles requests without validating a nonce token
  4. Check for nonce validation in the AJAX handler
    Locate the PHP file containing the getFollowsPage() function (commonly in the wpdiscuz/ajax/ directory or main class file) and search for 'wp_verify_nonce' or 'check_ajax_referer' calls within that function
    Affected if No nonce verification is present in the getFollowsPage() function handler

You are affected if wpDiscuz is installed with a version lower than 7.6.47 and the getFollowsPage() AJAX handler lacks nonce validation, allowing unauthorized follow data manipulation via CSRF.

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.47 or later
Fixed in 7.6.47
Interim mitigation

Update wpDiscuz to version 7.6.47 or later, which implements proper nonce validation for the getFollowsPage() function to prevent CSRF attacks.

Recommended fix High confidence

wpDiscuz 7.6.47

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate wpDiscuz in the plugin list
  4. 4. Check if an update to version 7.6.47 or later is available
  5. 5. If an update is available, click 'Update Now' to install the patched version
  6. 6. Alternatively, manually upload version 7.6.47 from wordpress.org/plugins/wpdiscuz/ if auto-update is not showing
  7. 7. After updating, verify the plugin is running version 7.6.47 or later under Plugins > Installed Plugins

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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