dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-12002

MEDIUM · 5.9 CVSS v3.1 Published 2026-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 Feeds for YouTube Pro plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 2.6.0 via the 'sby_check_wp_submit' AJAX action. This is due to insufficient sanitization of user-supplied data and the use of that data in a file operation. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information, granted the 'Save Featured Images' setting is enabled and 'Disable WP Posts' is disabled. Note: This vulnerability only affects the Pro version of Feeds for YouTube.

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 Feeds for YouTube Pro WordPress plugin versions up to 2.6.0 contains an arbitrary file read vulnerability in the 'sby_check_wp_submit' AJAX action. Due to insufficient sanitization of user-supplied input used in a file operation, unauthenticated attackers can read arbitrary files on the server. Exploitation requires the 'Save Featured Images' setting to be enabled and 'Disable WP Posts' to be disabled.

MitigationUpdate to version 2.6.1 or later when available. As a compensating control, disable the 'Save Featured Images' setting or enable 'Disable WP Posts' until the patch can be applied.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, locate 'Feeds for YouTube Pro', and note the version number displayed. Compare this to the affected range (versions up to 2.6.0).
    Affected if The installed version is 2.6.0 or lower.
  2. Verify the Save Featured Images setting
    In WordPress admin, navigate to the plugin settings for 'Feeds for YouTube Pro'. Look for a setting labeled 'Save Featured Images' and check whether it is enabled or disabled.
    Affected if The 'Save Featured Images' setting is enabled.
  3. Verify the Disable WP Posts setting
    In WordPress admin, navigate to the plugin settings for 'Feeds for YouTube Pro'. Look for a setting labeled 'Disable WP Posts' and check whether it is enabled or disabled.
    Affected if The 'Disable WP Posts' setting is disabled (not enabled).

A user is affected if the plugin version is 2.6.0 or lower AND the 'Save Featured Images' setting is enabled AND the 'Disable WP Posts' setting is disabled, as all three conditions are required for exploitation.

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 to version 2.6.1 or later when available. As a compensating control, disable the 'Save Featured Images' setting or enable 'Disable WP Posts' until the patch can be applied.

Recommended fix Moderate confidence

Feeds for YouTube Pro version 2.6.1 or later (any version after 2.6.0)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Feeds for YouTube Pro' plugin
  4. 4. Check the current version (should be 2.6.0 or earlier if vulnerable)
  5. 5. Go to Plugins > Add New > Upload Plugin (or check for updates within the plugin)
  6. 6. Upload and install the latest version of the Feeds for YouTube Pro plugin
  7. 7. Alternatively, download the latest version from smashballoon.com (the plugin developer's site)
  8. 8. After upgrade, verify the 'Save Featured Images' and 'Disable WP Posts' settings are appropriately configured under the plugin settings
Caveat Minor: Review plugin settings after upgrade as configuration may need re-verification; no major functionality changes expected from this security patch

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12002 — 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-12002 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