dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-13714

HIGH · 8.8 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 All-Images.ai – IA Image Bank and Custom Image creation plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the '_get_image_by_url' function in all versions up to, and including, 1.0.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 All-Images.ai WordPress plugin versions up to 1.0.4 lack file type validation in the '_get_image_by_url' function, allowing authenticated users with Subscriber-level permissions to upload arbitrary files to the server. This arbitrary file upload vulnerability can be leveraged for remote code execution.

MitigationUpdate to the latest plugin version when available, or implement proper file type validation and sanitization in the '_get_image_by_url' function to restrict uploads to expected file types only.

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
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 plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'All-Images.ai' and note the installed version number
    Affected if The installed version is 1.0.4 or lower (any version up to and including 1.0.4 is affected)
  2. Locate the vulnerable function in plugin code
    Access the plugin files via wp-content/plugins/all-images-ai/ directory and search for the '_get_image_by_url' function definition
    Affected if The function exists in the plugin code - this confirms the vulnerable code path is present
  3. Check file type validation in the function
    Examine the '_get_image_by_url' function code for any file type validation, MIME type checks, or extension validation logic before file write operations
    Affected if No file type validation or sanitization is performed before saving uploaded files
  4. Verify subscriber-level access to the vulnerable function
    In WordPress admin > Users > Roles and Capabilities, confirm that 'Subscriber' role exists and check if the plugin grants subscribers access to the image upload/import functionality
    Affected if Subscribers can access and trigger the '_get_image_by_url' function without elevated privileges

If the All-Images.ai plugin version is 1.0.4 or lower, the vulnerable '_get_image_by_url' function exists without file type validation, and Subscriber-level users can trigger it, the environment is affected by CVE-2024-13714

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 the latest plugin version when available, or implement proper file type validation and sanitization in the '_get_image_by_url' function to restrict uploads to expected file types only.

Recommended fix Moderate confidence

Version 1.0.5 or later (check WordPress plugin repository for latest stable release)

  1. Check the current version of the All-Images.ai plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the All-Images.ai plugin and verify the current version number
  4. Access the WordPress plugin repository or contact the plugin developer to obtain version 1.0.5 or later which should contain the fix for CVE-2024-13714
  5. Update the plugin to the latest available version that includes the file type validation fix
  6. Verify the update was successful and test that the '_get_image_by_url' function now properly validates file types
  7. Consider reviewing user roles and permissions to ensure only trusted users have Subscriber-level access until the patch is applied

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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