Unrestricted File UploadWeakness · CWE-434

CVE-2024-48027

CRITICAL · 9.9 CVSS v3.1 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unrestricted Upload of File with Dangerous Type vulnerability in xaraartech External featured image from bing external-featured-image-from-bing allows Upload a Web Shell to a Web Server.This issue affects External featured image from bing: from n/a through <= 1.0.2.

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 · moderate confidence

The xaraartech External Featured Image from Bing WordPress plugin allows uploading external images without proper file type validation, enabling attackers to upload malicious PHP files (web shells) directly to the web server. This unrestricted file upload vulnerability with dangerous type (CWE-434) provides remote code execution capability.

MitigationImmediately update the plugin to the latest patched version, or disable and remove the plugin if no patch exists. Additionally, configure the web server to disable PHP execution in the wp-content/uploads directory and audit the server for any existing malicious uploaded files.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify if the vulnerable plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'xaraartech External Featured Image from Bing' or check the wp-content/plugins directory for a folder containing 'xaraartech' in the name. Review the plugin version from the plugin header or readme.txt file.
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually in wp-content/plugins/xaraartech-external-featured-image-from-bing/) and look for the version header in the plugin comments, or check the version field in the plugin's main PHP file.
    Affected if The version cannot be verified as patched or is an older version prior to the vendor fix
  3. Inspect uploads directory for suspicious files
    Browse the wp-content/uploads directory (and subdirectories by year/month) using FTP, file manager, or command line. Look for files with .php, .php5, .phtml, or other executable extensions, especially those not originating from legitimate uploads.
    Affected if Any PHP or executable files exist in the uploads directory, particularly files with names that do not match expected media uploads
  4. Review plugin upload functionality configuration
    Navigate to the plugin settings in WordPress admin (usually under Media or a dedicated menu item for 'External Featured Image'). Check if the external image upload feature is enabled or has been configured.
    Affected if The external image upload feature is enabled and accessible to users
  5. Check server configuration for PHP execution in uploads
    Examine the web server configuration (Apache .htaccess, Nginx config) or wp-content/uploads directory for rules that block or allow PHP file execution. Look for directives like 'php_flag engine off' or equivalent Nginx settings.
    Affected if PHP execution is allowed in the wp-content/uploads directory (no blocking rules present)

A user is affected if the xaraartech External Featured Image from Bing plugin is installed with a vulnerable version, has the upload feature enabled, and either contains suspicious PHP files in uploads or allows PHP execution in the uploads directory.

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

Immediately update the plugin to the latest patched version, or disable and remove the plugin if no patch exists. Additionally, configure the web server to disable PHP execution in the wp-content/uploads directory and audit the server for any existing malicious uploaded files.

Recommended fix Moderate confidence

Latest available version of External featured image from bing plugin (newer than 1.0.2)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'External featured image from bing' (or 'external-featured-image-from-bing') plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the plugin is functioning correctly and test the featured image functionality
  6. 6. If no update is available in the WordPress admin, manually download the latest version from the WordPress Plugin Repository and reinstall
Caveat Review plugin changelog for any breaking changes before updating; test in staging environment first if possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-48027 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