CVE-2026-11370
Deferred Deferred - Pending Action

Server-Side Request Forgery in WP Meta SEO Plugin

Vulnerability report for CVE-2026-11370, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-24

Last updated on: 2026-06-29

Assigner: Wordfence

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-24
Last Modified
2026-06-29
Generated
2026-07-14
AI Q&A
2026-06-24
EPSS Evaluated
2026-07-13
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wp_meta_seo wp_meta_seo to 4.5.18 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The WP Meta SEO plugin for WordPress has a Server-Side Request Forgery (SSRF) vulnerability in all versions up to and including 4.5.18. This vulnerability exists via the 'new_link' parameter.

An authenticated attacker with contributor-level access or higher can exploit this flaw to make the web application send requests to arbitrary locations. This allows the attacker to query and modify information from internal services.

Additionally, the HTTP response status from these outbound requests is reflected back in the AJAX JSON response as status_code, which can be used as an enumeration oracle to probe internal hosts and cloud metadata services.

Impact Analysis

This vulnerability can allow an attacker with contributor-level access or higher to make the web application send requests to arbitrary internal or external locations.

Such unauthorized requests can be used to query and modify sensitive information from internal services that are normally inaccessible from outside.

The attacker can also use the reflected HTTP response status as a way to enumerate and probe internal hosts and cloud metadata services, potentially leading to further exploitation or information disclosure.

Compliance Impact

The vulnerability allows authenticated attackers with contributor-level access to perform Server-Side Request Forgery (SSRF), enabling them to make arbitrary web requests from the application and potentially query or modify internal services.

This can lead to unauthorized access or exposure of sensitive internal information, which may impact the confidentiality and integrity of data.

Such impacts could affect compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access or disclosure.

However, the provided context does not explicitly detail the direct compliance implications or specific regulatory impacts.

Detection Guidance

This vulnerability can be detected by monitoring for unusual outbound web requests originating from the WordPress application, especially those triggered via the 'new_link' parameter in AJAX requests. Since the HTTP response status from these outbound requests is reflected back in the AJAX JSON response as status_code, analyzing AJAX traffic for such patterns can help identify exploitation attempts.

Specific commands or detection scripts are not provided in the available resources.

Mitigation Strategies

Immediate mitigation steps include restricting contributor-level and higher users' ability to exploit the 'new_link' parameter by limiting access or disabling the vulnerable plugin until an update is applied.

Updating the WP Meta SEO plugin to a version later than 4.5.18, where this vulnerability is fixed, is recommended as a definitive mitigation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11370. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart