CVE-2025-12545
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Pixel Manager for WooCommerce – Track Conversions and Analytics, Google Ads, TikTok and more plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.49.2 via the ajax_pmw_get_product_ids() function due to insufficient restrictions on which products can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft products that they should not have access to.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Pixel Manager for WooCommerce plugin has an Information Exposure vulnerability in the ajax_pmw_get_product_ids() function. This function lacks proper access control checks, allowing unauthenticated attackers to retrieve metadata from password-protected, private, or draft products that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Pixel Manager for WooCommerce is installedCheck your WordPress plugins directory for the 'pixel-manager-for-woocommerce' folder, or look for the plugin in WordPress admin under PluginsAffected if The plugin is not installed on the WordPress site
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Pixel Manager for WooCommerce and read the version number from the plugin description; alternatively, check the main plugin file (e.g., woocommerce-pixel-manager.php) for the 'Version' headerAffected if Version is lower than 1.49.3 (vulnerable versions: < 1.49.3)
-
Confirm the vulnerable function existsInspect the plugin files for the function 'ajax_pmw_get_product_ids' - typically found in includes/class-ajax.php or similar AJAX handler files within the plugin directoryAffected if The function exists and is registered as an AJAX action (wp_ajax_ or wp_ajax_nopriv_) without capability checks
-
Verify presence of protected product typesIn WooCommerce, check Products > All Products for any products with status 'Private', 'Draft', or password-protected visibility settingsAffected if Any such products exist in the catalog and the plugin version is vulnerable
You are affected if Pixel Manager for WooCommerce is installed with a version lower than 1.49.3 and the site has private, draft, or password-protected products accessible via the ajax_pmw_get_product_ids AJAX endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to version 1.49.3 or later to patch the insufficient authorization checks in the ajax_pmw_get_product_ids() function.
1.49.3 or later
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate 'Pixel Manager for WooCommerce' plugin
- Click 'Update now' if an update is available, or manually update to version 1.49.3 or higher
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12545 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data