dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-9984

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-26
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 Featured Image from URL (FIFU) plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the fifu_api_debug_posts() function in all versions up to, and including, 5.2.7. This makes it possible for unauthenticated attackers to read private/password protected posts.

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 Featured Image from URL (FIFU) WordPress plugin versions up to 5.2.7 contain a missing capability check on the fifu_api_debug_posts() function. This allows unauthenticated attackers to invoke the function and access private or password-protected posts that should require authentication.

MitigationUpdate the FIFU plugin to version 5.2.8 or later. If a patch is not available, disable the plugin temporarily or deploy a WAF rule to block access to the vulnerable API endpoint until a fix is released.

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. Confirm FIFU plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Featured Image from URL' or 'FIFU' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'featured-image-from-url' or similar.
    Affected if The FIFU plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, find the FIFU plugin in Plugins > Installed Plugins and note the version number displayed below the plugin name. Alternatively, open /wp-content/plugins/featured-image-from-url/readme.txt and look for the 'Stable tag' entry.
    Affected if The version is 5.2.7 or lower (any version up to and including 5.2.7)
  3. Verify vulnerability is exploitable
    Send a request to the vulnerable endpoint. The function fifu_api_debug_posts() is typically accessible via a REST API route. Try accessing: /wp-json/fifu/v1/debug/posts or /?rest_route=/fifu/v1/debug/posts without any authentication. Check if the response contains post data.
    Affected if The API endpoint returns post data including private or password-protected posts without requiring authentication
  4. Check for private or protected content
    Review the response from the API endpoint (if accessible). Look for posts with 'status' set to 'private' or posts that have password protection. These should not be accessible to unauthenticated users.
    Affected if The API response includes posts with status 'private' or reveals password-protected post content without providing credentials

A user is affected if the FIFU plugin versions 5.2.7 or lower are installed AND the vulnerable /fifu/v1/debug/ REST API endpoint is publicly accessible and returns private or password-protected post data without authentication.

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 the FIFU plugin to version 5.2.8 or later. If a patch is not available, disable the plugin temporarily or deploy a WAF rule to block access to the vulnerable API endpoint until a fix is released.

Recommended fix Moderate confidence

5.2.8 or latest available version

  1. Update the Featured Image from URL (FIFU) WordPress plugin to the latest available version
  2. Verify the update was applied successfully in the WordPress admin plugins list
  3. Confirm that unauthenticated users can no longer access private or password-protected posts through the fifu_api_debug_posts() function

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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