CVE-2025-8084 is a Server-Side Request Forgery (SSRF) vulnerability identified in the tigroumeow AI Engine plugin for WordPress, affecting all versions up to and including 3.1.8. The vulnerability resides in the rest_helpers_create_images function, which improperly validates or restricts URLs that can be requested by the plugin. Authenticated attackers with Editor-level or higher privileges can exploit this flaw to induce the server to send HTTP requests to arbitrary locations, including internal network services or cloud metadata endpoints. This can lead to unauthorized information disclosure, such as internal IP addresses, service endpoints, or sensitive metadata that could facilitate further attacks or privilege escalation. The vulnerability requires authentication but no user interaction, and the attack scope is limited to users with elevated WordPress roles, which reduces the attack surface but still poses a significant risk in compromised or insider threat scenarios. The CVSS 3.1 base score is 6.8, reflecting medium severity with high confidentiality impact but no integrity or availability impact. No public exploits are known at this time, but the vulnerability is published and should be addressed promptly. The issue is particularly critical for cloud-hosted WordPress instances where metadata services can be queried, potentially exposing cloud credentials or configuration details. The vulnerability is classified under CWE-918, which covers SSRF issues that allow attackers to abuse server functionality to access or manipulate internal resources.

For European organizations, this vulnerability poses a risk of sensitive internal information disclosure, especially in environments where WordPress is used extensively and hosted on cloud infrastructure. Attackers with Editor-level access could leverage this SSRF to query internal services, potentially mapping internal networks or retrieving cloud metadata that may contain credentials or configuration data. This can facilitate lateral movement, privilege escalation, or further targeted attacks. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance risks if internal data is exposed. The impact on confidentiality is high, while integrity and availability remain unaffected. The requirement for authenticated access limits the attack vector but does not eliminate risk, particularly if credential compromise or insider threats exist. Cloud-hosted WordPress instances in Europe are especially vulnerable due to the ability to access cloud metadata services, which can lead to broader cloud environment compromise.

1. Restrict plugin access strictly to trusted users with Editor-level or higher privileges and review user roles regularly to minimize exposure. 2. Monitor and log outbound HTTP requests originating from the WordPress server to detect unusual or unauthorized internal requests. 3. Implement network segmentation and firewall rules to limit the WordPress server’s ability to access sensitive internal services and cloud metadata endpoints. 4. Apply principle of least privilege to WordPress users and service accounts to reduce the risk of exploitation. 5. Disable or restrict the vulnerable rest_helpers_create_images function if possible until a patch is available. 6. Stay updated with tigroumeow vendor advisories and apply security patches promptly once released. 7. Conduct internal penetration testing and vulnerability assessments focusing on SSRF and internal service exposure. 8. For cloud deployments, use cloud provider features to restrict metadata service access, such as metadata service versioning or access tokens. 9. Educate administrators and users about the risks of SSRF and the importance of credential security to prevent privilege abuse.