Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12159: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in muzaara Optimize Your Campaigns – Google Shopping – Google Ads – Google Adwords

0
Medium
VulnerabilityCVE-2024-12159cvecve-2024-12159cwe-200
Published: Tue Jan 07 2025 (01/07/2025, 04:22:19 UTC)
Source: CVE Database V5
Vendor/Project: muzaara
Product: Optimize Your Campaigns – Google Shopping – Google Ads – Google Adwords

Description

CVE-2024-12159 is an information exposure vulnerability in the WordPress plugin 'Optimize Your Campaigns – Google Shopping – Google Ads – Google Adwords' by muzaara, affecting all versions up to 3. 1. The vulnerability arises because the file print_php_information. php is publicly accessible without authentication, allowing attackers to retrieve sensitive configuration data. This exposure can aid attackers in crafting further attacks against the affected systems. The vulnerability has a CVSS 3. 1 score of 5. 3, indicating medium severity, with no known exploits in the wild currently. The attack requires no user interaction or privileges and can be executed remotely over the network. Organizations using this plugin on WordPress sites should prioritize restricting access to sensitive files and updating or patching the plugin when available.

AI-Powered Analysis

AILast updated: 02/26/2026, 06:16:16 UTC

Technical Analysis

CVE-2024-12159 is a medium-severity vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) found in the WordPress plugin 'Optimize Your Campaigns – Google Shopping – Google Ads – Google Adwords' developed by muzaara. The vulnerability exists in all plugin versions up to and including 3.1 due to the presence of a publicly accessible script named print_php_information.php. This script exposes sensitive PHP configuration and potentially other environment details without requiring any authentication or user interaction. Such information leakage can include database credentials, API keys, or server configuration details that attackers can leverage to escalate attacks, such as privilege escalation, code injection, or targeted exploitation of other vulnerabilities. The vulnerability is remotely exploitable over the network with low attack complexity and no privileges required, making it accessible to unauthenticated attackers. Although no known exploits have been reported in the wild, the exposure of sensitive configuration data poses a significant risk to confidentiality. The CVSS 3.1 base score is 5.3, reflecting the medium impact on confidentiality with no impact on integrity or availability. The plugin is used primarily by WordPress sites running Google Ads and Shopping campaigns, which are common in e-commerce and digital marketing sectors. The lack of a patch link suggests that users must manually mitigate or await an official update. This vulnerability highlights the importance of restricting access to sensitive files and careful plugin security hygiene in WordPress environments.

Potential Impact

The primary impact of CVE-2024-12159 is the unauthorized disclosure of sensitive configuration information, which can compromise the confidentiality of the affected systems. Attackers gaining access to such data may obtain database credentials, API keys, or other environment variables that can be used to further compromise the WordPress site or the underlying server. This can lead to subsequent attacks such as privilege escalation, data theft, or injection of malicious code. For organizations relying on this plugin to manage Google Ads and Shopping campaigns, exploitation could result in unauthorized manipulation of marketing campaigns, financial loss, reputational damage, and potential regulatory compliance issues if customer data is exposed. Since the vulnerability requires no authentication and can be exploited remotely, the attack surface is broad, especially for publicly accessible WordPress sites. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability becomes widely known. Overall, the impact is medium but could escalate if combined with other vulnerabilities or poor security practices.

Mitigation Recommendations

1. Immediately restrict access to the print_php_information.php file by implementing web server rules (e.g., .htaccess for Apache or location blocks for Nginx) to deny all external requests or limit access to trusted IP addresses only. 2. Remove or rename the print_php_information.php file if it is not essential for plugin functionality or debugging. 3. Monitor web server logs for any access attempts to this file and investigate suspicious activity. 4. Keep the plugin updated and monitor the vendor’s announcements for official patches addressing this vulnerability. 5. Employ a Web Application Firewall (WAF) to detect and block attempts to access sensitive files. 6. Conduct regular security audits of WordPress plugins and remove unused or unmaintained plugins. 7. Harden WordPress installations by following best practices, including least privilege principles for database and file permissions. 8. Educate site administrators about the risks of publicly exposing debug or configuration files. 9. If possible, isolate the plugin environment or run it in a sandboxed context to limit the impact of potential exploitation. 10. Consider implementing security plugins that can scan for exposed sensitive files and alert administrators.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-12-04T14:22:34.700Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e30b7ef31ef0b59769e

Added to database: 2/25/2026, 9:48:32 PM

Last enriched: 2/26/2026, 6:16:16 AM

Last updated: 2/26/2026, 8:08:29 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats