dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22201

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 7.6.47 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
wpDiscuz before 7.6.47 contains an IP spoofing vulnerability in the getIP() function that allows attackers to bypass IP-based rate limiting and ban enforcement by trusting untrusted HTTP headers. Attackers can set HTTP_CLIENT_IP or HTTP_X_FORWARDED_FOR headers to spoof their IP address and circumvent security controls.

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 an IP spoofing vulnerability in its getIP() function. The function trusts user-supplied HTTP headers (HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR) rather than validating the actual connection source IP. Attackers can set arbitrary values in these headers to bypass IP-based rate limits and bans.

MitigationUpdate wpDiscuz to version 7.6.47 or later, which addresses the IP spoofing issue. Alternatively, configure the web server to sanitize or strip untrusted proxy headers before requests reach the application.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 is installed
    Check your WordPress site's wp-content/plugins/ directory for the wpdiscuz folder, or look for wpDiscuz in the WordPress admin under Plugins.
    Affected if wpDiscuz plugin folder exists on the server
  2. Determine installed wpDiscuz version
    Open wp-content/plugins/wpdiscuz/readme.txt and locate the 'Stable tag' entry, or check the plugin header in wp-content/plugins/wpdiscuz/wpdiscuz.php for the 'Version' comment.
    Affected if Version is lower than 7.6.47 or version line cannot be found before that version number
  3. Locate the getIP() function
    Open the file wp-content/plugins/wpdiscuz/class/WpdiscuzCore.php (or similar main class file) and search for the string 'function getIP' to find the vulnerable function.
    Affected if The getIP() function exists and contains references to HTTP_CLIENT_IP or HTTP_X_FORWARDED_FOR without validation
  4. Confirm header trust behavior
    Within the getIP() function, verify it directly returns values from $_SERVER['HTTP_CLIENT_IP'] or $_SERVER['HTTP_X_FORWARDED_FOR'] without checking if the request actually came from a trusted proxy or validating against REMOTE_ADDR.
    Affected if The code uses user-supplied headers without validating the actual client IP from the connection

You are affected if wpDiscuz is installed and the version is below 7.6.47, as the getIP() function trusts client-supplied HTTP headers instead of validating the actual connection source IP.

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 addresses the IP spoofing issue. Alternatively, configure the web server to sanitize or strip untrusted proxy headers before requests reach the application.

Recommended fix High confidence

wpDiscuz version 7.6.47 or later

  1. Backup your WordPress database and files before making any changes
  2. Navigate to your WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find wpDiscuz in the plugin list
  5. Click 'Update now' if an update is available, or manually upload wpDiscuz version 7.6.47 or later
  6. After updating, verify the version number reflects 7.6.47 or higher
  7. Test that comments and rate limiting functionality still work correctly

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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