dbcve.org
All In One SeoWordPress extension · Aioseo

CVE-2022-42494

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to after 4.2.5.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Server Side Request Forgery (SSRF) vulnerability in All in One SEO Pro plugin <= 4.2.5.1 on 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) vulnerability in All in One SEO Pro plugin for WordPress versions 4.2.5.1 and below allows attackers to make the server perform arbitrary requests to internal or external resources.

MitigationUpdate All in One SEO Pro plugin to a version newer than 4.2.5.1 to patch the SSRF vulnerability.

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
All In One SeoWordPress extension
Affected:<= 4.2.5.1

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Confirm Aioseo plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins/aioseo directory via file manager or FTP
    Affected if The Aioseo (All in One SEO) plugin directory exists in the WordPress installation
  2. Identify the installed Aioseo plugin version
    Check the plugin version in the plugin header comment within aioseo/all_in_one_seo.php, or view the version in the WordPress Plugins admin page
    Affected if The displayed version number is 4.2.5.1 or lower
  3. Compare version against the affected range
    Review the version number found; the affected range is any version <= 4.2.5.1
    Affected if The installed version is 4.2.5.1 or below (for example, 4.2.5, 4.2.4, 4.1.0, etc.)
  4. Verify if the plugin has network request functionality enabled
    Check if any Aioseo settings allow external API calls, URL fetching, or backlink/SEO analysis features that could trigger the vulnerable endpoint
    Affected if Network request features are active and accessible to unauthenticated or low-privileged users

You are affected if the All in One SEO Pro plugin is installed and the version is 4.2.5.1 or lower, as this version range contains the SSRF vulnerability that allows arbitrary server requests.

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.

From vendor data
Upgrade available Upgrade to a release after 4.2.5.1
Interim mitigation

Update All in One SEO Pro plugin to a version newer than 4.2.5.1 to patch the SSRF vulnerability.

Fix this in All In One Seo Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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