CVE-2026-18059 json
PixelYourSite <= 11.2.1 - Unauthenticated Sensitive Information Exposure via Order-Received Endpoint Missing Key Validation
published 2026-08-01 3 mo ago modified 2026-08-12 2 mo ago also EUVD-2026-51760
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
The PixelYourSite – Your smart PIXEL (TAG) & API Manager plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 11.2.1 via the getWooPurchaseEventParams. This makes it possible for unauthenticated attackers to extract WooCommerce purchase metadata — including product names, product IDs, quantities, per-item prices, order totals, currency, and order/transaction IDs — for any existing order by supplying an invalid or arbitrary order key. This is exploitable against any known or enumerated order ID, as the plugin resolves the order from the URL path variable alone and emits the full woo_purchase tracking payload into the page HTML via the pysOptions JavaScript object across its Facebook, Google Analytics, and Google Tag Manager integrations regardless of key validity.
Patch / fix
- pixelyoursite PixelYourSite Pro – Your smart PIXEL (TAG) Manager 12.6.1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- pixelyoursite PixelYourSite – Your smart PIXEL (TAG) & API Manager
- pixelyoursite PixelYourSite Pro – Your smart PIXEL (TAG) Manager
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ca14ec54-0864-47f7-9653-1fe04e2875de?source=cve
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.1/modules/facebook/facebook.php#L696
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.1/modules/google_analytics/ga.php#L843
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.1/modules/google_gtm/gtm.php#L1083
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.1/includes/functions-woo.php#L244
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.1/includes/class-pys.php#L1112
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.0.5/modules/facebook/facebook.php#L696
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.0.5/modules/google_analytics/ga.php#L843
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.0.5/modules/google_gtm/gtm.php#L1083
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.0.5/includes/functions-woo.php#L244
- plugins.trac.wordpress.org /browser/pixelyoursite/tags/11.2.0.5/includes/class-pys.php#L1112
- plugins.trac.wordpress.org /changeset?reponame=&old=3629756%40pixelyoursite&new=3629756%40pixelyoursite
Sources
- CVE List CVE-2026-18059
- NVD CVE-2026-18059
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.