CVE-2026-16600 Overview
CVE-2026-16600 is a Server-Side Request Forgery (SSRF) vulnerability in the SmartAIPress WordPress plugin through version 1.2.0. The plugin exposes an AJAX action that lacks a capability check and fails to validate user-supplied URLs before fetching them server-side. Any authenticated user with subscriber-level access or above can coerce the WordPress site to issue HTTP requests to arbitrary internal or external endpoints and read the full response body. The flaw is tracked under CWE-918.
Critical Impact
Low-privileged subscribers can pivot the WordPress host into internal networks, reach cloud metadata services, and exfiltrate sensitive response data through a full-read SSRF.
Affected Products
- SmartAIPress WordPress plugin, all versions through 1.2.0
- WordPress installations exposing the vulnerable AJAX action to authenticated users
- Hosts co-located with internal HTTP services or cloud metadata endpoints
Discovery Timeline
- 2026-08-29 - CVE-2026-16600 published to NVD
- 2026-08-31 - Last updated in NVD database
Technical Details for CVE-2026-16600
Vulnerability Analysis
The SmartAIPress plugin registers an AJAX action available to authenticated WordPress users. The handler accepts a URL parameter, performs a server-side HTTP request, and returns the response body to the caller. Two independent failures combine into a full-read SSRF. First, the handler omits a WordPress capability check, so any authenticated role including subscriber can invoke it. Second, the handler does not validate or filter the supplied URL against an allowlist, deny private address ranges, or restrict schemes.
Because WordPress permits open subscriber registration on many sites, the effective attacker prerequisite is minimal. The response body is returned verbatim, which enables reading of internal APIs, admin panels bound to localhost, and cloud instance metadata services such as 169.254.169.254. This turns the WordPress host into an authenticated proxy into otherwise unreachable network segments.
Root Cause
The root cause is missing authorization and missing input validation on a server-initiated fetch. WordPress AJAX endpoints registered through wp_ajax_{action} are accessible to any logged-in user unless the handler explicitly enforces current_user_can() or a nonce tied to a privileged capability. SmartAIPress performs neither the authorization check nor URL sanitization before invoking its HTTP client.
Attack Vector
An attacker registers or uses an existing subscriber account, then issues a POST request to /wp-admin/admin-ajax.php with the vulnerable action and a controlled URL parameter. The plugin fetches the URL from the WordPress host and returns the raw response. Attackers commonly target cloud metadata endpoints to steal temporary IAM credentials, internal Elasticsearch or Redis interfaces, and intranet applications that trust source IPs. See the WPScan Vulnerability Report for technical details.
Detection Methods for CVE-2026-16600
Indicators of Compromise
- Outbound HTTP requests from the WordPress host to RFC1918 addresses, 127.0.0.1, or 169.254.169.254 that originate from the PHP worker process.
- POST requests to /wp-admin/admin-ajax.php referencing the SmartAIPress AJAX action with a url or similar parameter containing an external or internal host.
- Unusual subscriber accounts created shortly before anomalous AJAX activity.
Detection Strategies
- Alert on admin-ajax.php requests carrying URL-shaped parameters when the authenticated role is subscriber or lower.
- Correlate PHP-FPM egress connections with WordPress access logs to identify server-initiated fetches driven by user input.
- Inspect web server logs for repeated AJAX calls returning large response bodies to a single low-privileged account.
Monitoring Recommendations
- Log and retain full admin-ajax.php request bodies for the SmartAIPress action set.
- Monitor egress to link-local and private ranges from web application tiers and alert on any hit.
- Review new subscriber registrations against subsequent AJAX activity within short time windows.
How to Mitigate CVE-2026-16600
Immediate Actions Required
- Deactivate the SmartAIPress plugin on all sites running version 1.2.0 or earlier until a patched release is confirmed.
- Disable open user registration or restrict the default role to a custom role with no AJAX access.
- Block egress from the WordPress host to 169.254.169.254 and internal management ranges at the network layer.
Patch Information
At the time of the NVD entry, no fixed version is listed for SmartAIPress. The vulnerability applies to all releases through 1.2.0. Monitor the WPScan advisory and the plugin's WordPress.org listing for a patched build, and update immediately when available.
Workarounds
- Enforce IMDSv2 on AWS instances so metadata credential theft requires a session token that SSRF cannot obtain.
- Deploy a web application firewall rule that blocks admin-ajax.php requests referencing the vulnerable action from non-administrator sessions.
- Restrict PHP outbound network access with an egress proxy allowlist covering only required third-party APIs.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
