Description

The SmartAIPress WordPress plugin through 1.2.0 does not perform a capability check on one of its AJAX actions and does not validate a user-supplied URL before fetching it server-side, allowing users with subscriber-level access and above to make the site retrieve arbitrary internal or external URLs and read the response, resulting in a full-read Server-Side Request Forgery.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.7",
  "pubDate": "2026-08-29T06:17:05.443Z",
  "pubdate": "2026-08-29T06:17:05.443Z",
  "executiveSummary": "The SmartAIPress WordPress plugin, in all versions up to and including 1.2.0, contains a critical Server-Side Request Forgery (SSRF) vulnerability. This flaw stems from a lack of access control and input validation within the plugin's AJAX request handling mechanism. By failing to perform authorization checks or sanitize user-supplied input, the plugin allows authenticated users—specifically those with subscriber-level permissions or higher—to force the hosting server to perform unauthorized HTTP requests to arbitrary internal or external targets.\nThe impact of this vulnerability is significant, as it enables attackers to bypass network perimeters, perform internal network reconnaissance, and interact with services restricted to the local network environment (such as internal APIs, cloud metadata services, or administrative interfaces). Because the server returns the contents of the fetched URL to the requester, attackers can exfiltrate sensitive data or interact with services that rely on IP-based trust. This vulnerability poses a severe risk to the confidentiality and integrity of the affected WordPress installation and its underlying infrastructure.",
  "technicalDetails": "The vulnerability resides in an unauthenticated or improperly authorized AJAX action implemented within the SmartAIPress plugin. The root cause is a dual failure: the complete absence of capability checks for a privileged administrative operation and the lack of URL validation or server-side filtering on user-controlled parameters passed to the request-handling function.\nThe attack flow begins when an attacker, authenticated as a subscriber, identifies the AJAX endpoint responsible for remote resource fetching. By sending a crafted POST request to the WordPress admin-ajax.php handler, the attacker specifies a target URI through a vulnerable parameter. Since the backend code lacks a whitelist for permitted domains or URI schemes, the plugin initiates an HTTP request using the server's internal context to the attacker-supplied URL.\nUpon receiving the request, the target service (whether external or internal) processes the request as if it originated from the legitimate web server. For internal targets, this bypasses firewalls or network access control lists (ACLs) that would otherwise prevent external access. The response from the target is then returned to the attacker through the AJAX response, completing the full-read SSRF cycle.\nThis vulnerability is particularly dangerous when the web server is hosted in cloud environments (e.g., AWS, GCP, Azure), as an attacker can potentially reach the instance metadata service (e.g., 169.254.169.254) to extract temporary IAM security credentials or configuration data. Furthermore, the attacker can leverage the server as a proxy to perform port scanning on the local loopback interface or other hosts within the internal network to identify further vulnerabilities or reachable services. The lack of restriction on protocols or destination addresses transforms the plugin into an arbitrary request oracle, significantly expanding the attack surface of the host environment."
}