PixelYourSite <= 11.1.2 – Cross-Site Request Forgery to GDPR Options Modification
Strategic Overview
- Status
- Patched in 11.1.3
- Affected Plugin
- PixelYourSite – Your smart PIXEL (TAG) & API Manager
- Affected Version
<= 11.1.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-10588
At a glance
CVE-2025-10588 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PixelYourSite WordPress plugin, affecting versions <= 11.1.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 11.1.3; sites on affected versions should update now. Disclosed October 2025, reported by Dmitrii Ignatyev.
Vulnerability Overview
The PixelYourSite – Your smart PIXEL (TAG) & API Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 11.1.2. This is due to missing or incorrect nonce validation on the adminEnableGdprAjax() function. This makes it possible for unauthenticated attackers to modify GDPR settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
PixelYourSite <= 11.1.2 carries this weakness at adminEnableGdprAjax(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PixelYourSite the fix is 11.1.3: builds <= 11.1.2 are affected, anything from 11.1.3 onward is not.
Remediation
Update to version 11.1.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PixelYourSite: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PixelYourSite 11.1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in PixelYourSite – Your smart PIXEL (TAG) & API Manager
- 8.1CVE-2025-0769: PixelYourSite PHP Object Injection
CVE-2025-0769 - 7.2CVE-2026-1841: PixelYourSite <= 11.2.0 Stored Cross-Site Scripting
CVE-2026-1841 - 6.6CVE-2025-10723: PixelYourSite – Your smart PIXEL (TAG) Manager LFI
CVE-2025-10723 - 6.5CVE-2024-7870: PixelYourSite and PixelYourSite PRO <= 10.4.2
CVE-2024-7870 - 5.4CVE-2018-0578: PixelYourSite <= 5.2.1 Reflected Cross-Site Scripting
CVE-2018-0578 - 5.3CVE-2026-18059: PixelYourSite <= 11.2.1 Sensitive Information Exposure
CVE-2026-18059 - 5.3CVE-2025-14280: PixelYourSite <= 11.1.5 Sensitive Information Exposure
CVE-2025-14280 - 4.4CVE-2024-37447: PixelYourSite – Your smart PIXEL Manager Stored XSS
CVE-2024-37447
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C