dbcve.org
SeoWordPress extension · Rankmath

CVE-2022-36376

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to after 1.0.95 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Server-Side Request Forgery (SSRF) vulnerability in Rank Math SEO plugin <= 1.0.95 at WordPress.

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

Server-Side Request Forgery (SSRF) in Rank Math SEO plugin versions 1.0.95 and below allows unauthenticated attackers to induce the WordPress server to make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services, cloud metadata endpoints, or bypassing network segmentation.

MitigationUpdate Rank Math SEO plugin to the latest version (>1.0.95) to apply the vendor patch, or remove the plugin if not needed. If immediate update is not possible, consider restricting outbound access at the network layer.

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
SeoWordPress extension
Affected:<= 1.0.95

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Rank Math SEO plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Rank Math SEO and note the version number displayed, or query the plugin version via wp-cli: wp plugin list --name=rank-math --format=json
    Affected if The installed version is 1.0.95 or any version lower than 1.0.95
  2. Verify plugin is active
    Confirm the Rank Math SEO plugin status in WordPress admin under Plugins > Installed Plugins, or query: wp plugin status rank-math
    Affected if The plugin is active and the version is 1.0.95 or below
  3. Review server access logs for unusual outbound requests
    Examine web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for requests originating from your server to unusual internal or external endpoints that you did not initiate
    Affected if Logs show HTTP requests from your server to internal IP ranges (127.0.0.1, 169.254.169.254, 10.x.x.x, 192.168.x.x) or unexpected external domains that were not triggered by legitimate admin actions
  4. Check for suspicious callback endpoints
    Review WordPress REST API logs or server logs for POST requests to /?rest_route=/rankmath/v1/ or similar Rank Math AJAX endpoints with unusual URL parameters
    Affected if Requests contain parameters specifying attacker-controlled URLs being requested by the server

Your environment is affected if the Rank Math SEO plugin is active and the installed version is 1.0.95 or lower, and particularly if logs show unexpected outbound requests from the server.

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 a release after 1.0.95
Interim mitigation

Update Rank Math SEO plugin to the latest version (>1.0.95) to apply the vendor patch, or remove the plugin if not needed. If immediate update is not possible, consider restricting outbound access at the network layer.

Recommended fix Moderate confidence

Rank Math SEO version 1.0.96 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Rank Math SEO plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the updated version is 1.0.96 or higher after updating

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

Fix this in Seo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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