Overview
The CVE-2025-7327 vulnerability involves the Widget for Google Reviews plugin for WordPress, which has been found susceptible to Directory Traversal. This vulnerability is significant as it affects all versions of the plugin up to 1.0.15. The vulnerability can be exploited by authenticated attackers with Subscriber-level access and above, to include and execute arbitrary files on the server. This poses a serious cybersecurity threat as it permits the execution of any PHP code in those files and can lead to potential system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-7327
Severity: High (8.8 CVSS Severity Score)
Attack Vector: Network
Privileges Required: Low (Subscriber-level access and above)
User Interaction: Required
Impact: Execution of arbitrary PHP code, leading to potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Widget for Google Reviews WordPress Plugin | Up to, and including, 1.0.15
How the Exploit Works
The exploit works by manipulating the ‘layout’ parameter of the plugin. An attacker with at least subscriber-level access can leverage this vulnerability to include and execute arbitrary files on the server. This includes any PHP code contained within those files, even in cases where only images and other traditionally “safe” file types are allowed to be uploaded. This can result in bypassing access controls, obtaining sensitive data, or executing code, ultimately leading to a potential system compromise or data leakage.
Conceptual Example Code
Here is a conceptual example of how an HTTP request exploiting this vulnerability might look:
POST /wp-admin/admin-ajax.php?action=wprev-slider-preview HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
layout=../../../../wp-config.php%00In this example, the attacker attempts to traverse the directory to include the ‘wp-config.php’ file, a critical WordPress configuration file containing sensitive information. The inclusion and execution of this file could have serious implications, including compromise of the entire system or data leakage.