dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-14280

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The PixelYourSite WordPress plugin exposes sensitive log files publicly when the 'Meta API logs' setting is enabled. Unauthenticated attackers can access these logs to view potentially sensitive information. The vulnerability affects versions up to 11.1.5, with partial patching in 11.1.5 and full patching in 11.1.5.1.

MitigationUpdate PixelYourSite plugin to version 11.1.5.1 or later. Ensure the 'Meta API logs' setting remains disabled (default) as an additional security measure.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PixelYourSite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PixelYourSite' or run 'wp plugin list --name="pixelyoursite"' via WP-CLI
    Affected if PixelYourSite plugin is not installed or version is 11.1.5.1 or later (full patch applied)
  2. Check installed plugin version
    View the plugin version in the WordPress plugins list or read the main plugin file (wp-content/plugins/pixelyoursite/header comment) to compare against 11.1.5.1
    Affected if Installed version is 11.1.5 or earlier (vulnerable)
  3. Confirm Meta API logs setting status
    In WordPress admin, go to PixelYourSite > Settings > Meta (Facebook) tab and look for 'Meta API logs' checkbox or check the wp_options table for option_name containing 'pys_meta_api_logs' or similar
    Affected if Meta API logs setting is ENABLED (checked/on)
  4. Identify publicly accessible log files
    Check wp-content/uploads/pixelyoursite/logs/ or similar paths for .log files accessible via web browser (try accessing a log URL directly without authentication)
    Affected if Log files exist in web-accessible directories and are publicly downloadable without authentication

You are affected if PixelYourSite versions 11.1.5 or earlier are installed AND the Meta API logs setting is enabled, allowing unauthenticated access to sensitive log data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update PixelYourSite plugin to version 11.1.5.1 or later. Ensure the 'Meta API logs' setting remains disabled (default) as an additional security measure.

Recommended fix High confidence

PixelYourSite version 11.1.5.1

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find PixelYourSite in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 11.1.5.1
  5. Alternatively, download version 11.1.5.1 from the WordPress plugin repository and upload it manually
  6. After updating, verify the plugin is running version 11.1.5.1 under Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14280 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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