dbcve.org
Auto Featured ImageWordPress extension · Auto Featured Image Project

CVE-2024-6054

HIGH · 8.8 CVSS v3.1 Published 2024-06-27
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Auto Featured Image plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'create_post_attachment_from_url' function in all versions up to, and including, 1.2. This makes it possible for authenticated attackers, with contributor-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Auto Featured Image WordPress plugin lacks file type validation in its create_post_attachment_from_url function, allowing authenticated users with contributor-level permissions or higher to upload arbitrary files to the server, which can be leveraged for remote code execution.

MitigationUpdate the plugin to the latest version immediately. If no update is available, disable or remove the plugin. Audit the uploads directory for any malicious files that may have been uploaded.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Auto Featured ImageWordPress extension
Affected:<= 1.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 the Auto Featured Image plugin is installed
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Auto Featured Image' in the list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view details to see the version number displayed
    Affected if The version listed is 1.2 or lower
  3. Confirm the vulnerable function exists in the codebase
    Via file manager or FTP, navigate to wp-content/plugins/auto-featured-image and locate the file containing create_post_attachment_from_url function; this is typically in the main plugin file
    Affected if The function create_post_attachment_from_url exists in the plugin files
  4. Identify users with contributor-level or higher access
    In WordPress admin, go to Users > All Users and review the role column for any accounts assigned Contributor, Author, Editor, or Administrator roles
    Affected if There are one or more users with contributor, author, editor, or administrator roles
  5. Inspect the uploads directory for suspicious files
    Via file manager or FTP, examine wp-content/uploads/ for any unfamiliar PHP files, scripts, or files with double extensions (e.g., image.php.jpg) that were uploaded unexpectedly
    Affected if Unexpected or malicious files are present in the uploads directory

You are affected if the Auto Featured Image plugin is installed at version 1.2 or lower and you have users with contributor-level or higher permissions, as the missing file type validation allows arbitrary file uploads via the create_post_attachment_from_url function.

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.

From vendor data
Upgrade available Upgrade to a release after 1.2
Interim mitigation

Update the plugin to the latest version immediately. If no update is available, disable or remove the plugin. Audit the uploads directory for any malicious files that may have been uploaded.

Fix this in Auto Featured Image Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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