PixelYourSite – Your smart PIXEL (TAG) & API Manager <= 9.7.1 and PixelYourSite PRO <= 10.4.2 - Unauthenticated Information Exposure and Log Deletion
Strategic Overview
- Status
- Patched in 9.7.2
- Affected Plugin
- PixelYourSite – Your smart PIXEL (TAG) & API Manager
- Affected Version
<= 9.7.1- CVSS
- 6.5Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2024-7870
At a glance
CVE-2024-7870 is a medium-severity Improper Authentication vulnerability in the PixelYourSite WordPress plugin, affecting versions <= 9.7.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 9.7.2; sites on affected versions should update now. Disclosed September 2024, reported by Xetnus.
Vulnerability Overview
The PixelYourSite – Your smart PIXEL (TAG) & API Manager and the PixelYourSite PRO plugins for WordPress are vulnerable to Sensitive Information Exposure in all versions up to, and including, 9.7.1 and 10.4.2, respectively, through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log files, and to delete log files.
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, and no interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in PixelYourSite <= 9.7.1 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For PixelYourSite the fix is 9.7.2: builds <= 9.7.1 are affected, anything from 9.7.2 onward is not.
Remediation
Update to version 9.7.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PixelYourSite 9.7.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
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 - 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 - 4.4CVE-2023-2584: PixelYourSite and PixelYourSite Pro <= 9.6.1
CVE-2023-2584
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C