dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-11370

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
The WP Meta SEO plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.5.18 via the 'new_link' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The HTTP response status from outbound requests is reflected back in the AJAX JSON response as status_code, providing an enumeration oracle usable for probing internal hosts and cloud metadata services.

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

The WP Meta SEO plugin for WordPress versions up to 4.5.18 contains an unauthenticated SSRF vulnerability via the 'new_link' parameter. Authenticated attackers with contributor-level access can make arbitrary HTTP requests from the server and receive reflected HTTP status codes in AJAX responses, enabling probing of internal hosts and cloud metadata services.

MitigationUpdate WP Meta SEO plugin to version beyond 4.5.18 when available; until then, restrict contributor-level user permissions and implement server-side URL allowlist validation for the 'new_link' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify WP Meta SEO plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'WP Meta SEO' in the list. Note the version number displayed below the plugin name.
    Affected if Plugin is present and version is 4.5.18 or lower
  2. Confirm installed version number
    In the plugins list, check the 'Version' column for WP Meta SEO. If not visible, click the plugin name to view its details page where the version is listed.
    Affected if Version is 4.5.18 or any version up to and including 4.5.18
  3. Identify contributor-level user accounts
    Go to Users > All Users in WordPress admin. Review the 'Role' column for any accounts with 'Contributor' role assigned.
    Affected if At least one user account has Contributor role enabled
  4. Locate the vulnerable AJAX endpoint
    Inspect plugin files (typically in wp-content/plugins/wp-meta-seo/) for AJAX handlers that process the 'new_link' parameter. Common paths include ajax.php, class-ajax.php, or functions handling link meta operations.
    Affected if The plugin processes 'new_link' parameter via AJAX without proper URL validation
  5. Test for contributor access to the endpoint
    Using a contributor-level test account, attempt to access the AJAX endpoint that handles the 'new_link' parameter. Observe if the request is accepted and HTTP response codes are reflected in the AJAX response.
    Affected if Contributor users can submit arbitrary URLs via 'new_link' and receive reflected HTTP status codes

You are affected if WP Meta SEO plugin version 4.5.18 or lower is installed AND contributor-level user accounts exist in WordPress, as the vulnerability allows those users to perform SSRF attacks via the 'new_link' parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Meta SEO plugin to version beyond 4.5.18 when available; until then, restrict contributor-level user permissions and implement server-side URL allowlist validation for the 'new_link' parameter.

Recommended fix Moderate confidence

Version 4.5.19 or later

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate WP Meta SEO in the plugin list
  3. Check the current installed version (should be 4.5.18 or earlier)
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/wp-meta-seo
  5. After updating, verify the version number reflects the new release (4.5.19 or later)
Caveat Minor plugin update; review changelog for any template or setting changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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