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-14280: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in pixelyoursite PixelYourSite – Your smart PIXEL (TAG) & API Manager

0
Medium
VulnerabilityCVE-2025-14280cvecve-2025-14280cwe-200
Published: Mon Dec 29 2025 (12/29/2025, 18:20:49 UTC)
Source: CVE Database V5
Vendor/Project: pixelyoursite
Product: PixelYourSite – Your smart PIXEL (TAG) & API Manager

Description

The PixelYourSite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 11.1.5 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log files, when the "Meta API logs" setting is enabled (disabled by default). The vulnerability was partially patched in version 11.1.5 and fully patched in version 11.1.5.1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:03:13 UTC

Technical Analysis

CVE-2025-14280 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting the PixelYourSite WordPress plugin, a popular tool for managing pixels, tags, and APIs. The flaw arises from publicly exposed log files generated when the 'Meta API logs' feature is enabled. These log files can contain sensitive information such as API keys, user data, or other metadata that should remain confidential. Because the logs are publicly accessible without authentication or user interaction, any attacker can retrieve this information simply by accessing the log file URLs. The vulnerability affects all versions up to and including 11.1.5. A partial patch was introduced in version 11.1.5, but the issue was fully resolved in version 11.1.5.1. The CVSS v3.1 base score is 5.3, reflecting a medium severity due to the vulnerability's ease of exploitation (network accessible, no privileges required) but limited impact (confidentiality only, no integrity or availability impact). No known exploits have been reported in the wild, but the risk remains for organizations that have enabled the logging feature and have not updated to the patched version. The vulnerability highlights the importance of secure logging practices and access controls for sensitive diagnostic data in web applications and plugins.

Potential Impact

The primary impact of this vulnerability is the unauthorized disclosure of sensitive information contained in the exposed log files. This can lead to information leakage that may facilitate further attacks, such as credential theft, API abuse, or reconnaissance by malicious actors. Although the vulnerability does not affect data integrity or system availability, the confidentiality breach can undermine organizational security, especially if the logs contain API keys, user identifiers, or other sensitive metadata. Organizations running WordPress sites with PixelYourSite plugin versions up to 11.1.5 and with the 'Meta API logs' enabled are at risk. The exposure is particularly concerning for websites handling sensitive user data or critical business operations. The lack of authentication or user interaction required for exploitation increases the risk, as attackers can easily access the logs remotely. However, since the logging feature is disabled by default, the scope of affected systems is somewhat limited to those who have explicitly enabled it.

Mitigation Recommendations

1. Immediately update the PixelYourSite plugin to version 11.1.5.1 or later, where the vulnerability is fully patched. 2. Verify and disable the 'Meta API logs' setting unless logging is absolutely necessary for troubleshooting, as it is disabled by default. 3. If logging must be enabled, restrict access to the log files using web server access controls (e.g., .htaccess rules, IP whitelisting) or authentication mechanisms to prevent unauthorized access. 4. Regularly audit web server directories and plugin files to ensure no sensitive logs or debug files are publicly accessible. 5. Implement monitoring and alerting for unusual access patterns to log files or plugin directories. 6. Educate site administrators about the risks of enabling verbose logging features without proper access controls. 7. Review and rotate any potentially exposed API keys or credentials that may have been logged prior to patching. 8. Employ a web application firewall (WAF) to detect and block suspicious requests targeting plugin log files.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-08T17:15:54.201Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695450b3db813ff03e2beed8

Added to database: 12/30/2025, 10:22:43 PM

Last enriched: 2/27/2026, 11:03:13 AM

Last updated: 3/26/2026, 4:42:02 AM

Views: 113

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 for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses