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-2025-12545: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in alekv Pixel Manager for WooCommerce – Track Conversions and Analytics, Google Ads, TikTok and more

0
Medium
VulnerabilityCVE-2025-12545cvecve-2025-12545cwe-200
Published: Tue Nov 18 2025 (11/18/2025, 13:54:50 UTC)
Source: CVE Database V5
Vendor/Project: alekv
Product: Pixel Manager for WooCommerce – Track Conversions and Analytics, Google Ads, TikTok and more

Description

CVE-2025-12545 is a medium-severity vulnerability in the Pixel Manager for WooCommerce WordPress plugin that allows unauthenticated attackers to access sensitive product data, including password-protected, private, or draft products. The flaw exists due to insufficient access control in the ajax_pmw_get_product_ids() function, enabling unauthorized data exposure without requiring authentication or user interaction. This vulnerability impacts all versions up to and including 1. 49. 2. While no known exploits are currently active in the wild, the ease of exploitation and the exposure of confidential product information pose risks to affected e-commerce sites. European organizations using WooCommerce with this plugin are at risk of sensitive data leakage, potentially harming business confidentiality and customer trust. Mitigation involves promptly updating the plugin once a patch is released or applying custom access control restrictions to the vulnerable AJAX endpoint. Countries with high WooCommerce adoption and significant e-commerce activity, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the medium CVSS score of 5.

AI-Powered Analysis

AILast updated: 11/25/2025, 14:27:08 UTC

Technical Analysis

The vulnerability identified as CVE-2025-12545 affects the Pixel Manager for WooCommerce – Track Conversions and Analytics, Google Ads, TikTok and more plugin for WordPress, specifically versions up to 1.49.2. The root cause lies in the ajax_pmw_get_product_ids() function, which lacks sufficient access control checks to restrict which product IDs can be queried via AJAX requests. This flaw allows unauthenticated attackers to retrieve data from products that are intended to be protected, including password-protected, private, or draft products. Since WooCommerce is a widely used e-commerce platform on WordPress, this plugin is commonly deployed to manage tracking pixels for marketing and analytics purposes. The vulnerability is classified under CWE-200, indicating exposure of sensitive information to unauthorized actors. The CVSS v3.1 base score is 5.3, reflecting a medium severity level with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact is limited to confidentiality, with no direct integrity or availability effects. No known exploits have been reported in the wild to date. The vulnerability was reserved on October 31, 2025, and published on November 18, 2025. No official patches or updates are currently linked, so mitigation may require temporary workarounds or monitoring for forthcoming updates from the vendor.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive product information, including unreleased or confidential product details that could be leveraged by competitors or malicious actors. Exposure of private or draft product data may result in reputational damage, loss of customer trust, and potential financial harm if sensitive marketing or pricing strategies are revealed prematurely. Since the vulnerability does not require authentication or user interaction, any attacker with network access to the affected WordPress site could exploit it remotely. This increases the risk profile for e-commerce businesses relying on WooCommerce and this plugin. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach alone can have significant business impact, especially for companies with strict data protection requirements under GDPR. Additionally, attackers could combine this information exposure with other attacks to escalate their foothold or conduct targeted phishing campaigns.

Mitigation Recommendations

1. Monitor the vendor’s official channels for a security patch addressing CVE-2025-12545 and apply updates immediately upon release. 2. Until a patch is available, implement custom access control on the ajax_pmw_get_product_ids() AJAX endpoint to restrict requests to authenticated and authorized users only. 3. Employ Web Application Firewalls (WAFs) to detect and block suspicious AJAX requests targeting this function, especially those originating from unauthenticated sources. 4. Review and harden WordPress and WooCommerce security configurations, including limiting plugin permissions and disabling unnecessary AJAX endpoints. 5. Conduct regular audits of product visibility settings to ensure sensitive products are properly protected. 6. Educate development and security teams about this vulnerability to increase awareness and readiness for incident response. 7. Consider isolating or segmenting e-commerce infrastructure to limit exposure in case of exploitation. 8. Implement comprehensive logging and monitoring to detect anomalous access patterns related to product data retrieval.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-31T11:20:54.685Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691c7c583fd37bbc39576645

Added to database: 11/18/2025, 2:02:00 PM

Last enriched: 11/25/2025, 2:27:08 PM

Last updated: 1/7/2026, 4:23:19 AM

Views: 99

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