dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-31114

CRITICAL · 9.1 CVSS v3.1 Published 2024-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/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 biplob018 Shortcode Addons.This issue affects Shortcode Addons: from n/a through 3.2.5.

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

An unrestricted file upload vulnerability in the biplob018 Shortcode Addons plugin (versions through 3.2.5) allows attackers to upload dangerous file types without proper validation, potentially leading to remote code execution.

MitigationRestrict file uploads to only permitted MIME types and file extensions, implement server-side validation of file content (not just extension), and store uploads outside webroot or with executable permissions removed.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm plugin installation
    Locate the Shortcode Addons plugin directory in the WordPress plugins folder (wp-content/plugins/) and identify if a folder named 'shortcode-addons' or similar exists.
    Affected if The plugin directory is present on the server
  2. Check installed version
    Open the main plugin file (usually shortcode-addons.php) or the readme.txt file in the plugin directory and locate the Version header. Compare this version number to 3.2.5.
    Affected if The reported version is 3.2.5 or lower
  3. Verify upload functionality exposure
    Access the WordPress admin panel and navigate to the Shortcode Addons settings. Look for any file upload, media upload, or content import features that accept user-supplied files.
    Affected if A file upload or import feature is enabled and accessible
  4. Inspect file validation configuration
    Examine the plugin settings or source code for MIME type validation, file extension checking, and content-type verification on any upload handlers.
    Affected if No server-side MIME type or content validation is configured for uploads
  5. Check uploaded file storage location
    Review the wp-content/uploads directory structure and verify if uploaded files are stored inside the webroot and retain executable permissions.
    Affected if Uploaded files are stored within the web-accessible directory without execution restrictions

A user is affected if the Shortcode Addons plugin versions 3.2.5 or lower is installed with an accessible file upload feature that lacks proper MIME type and content validation.

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

Restrict file uploads to only permitted MIME types and file extensions, implement server-side validation of file content (not just extension), and store uploads outside webroot or with executable permissions removed.

Recommended fix Moderate confidence

Latest version of Shortcode Addons plugin (version higher than 3.2.5)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update the Shortcode Addons plugin to the latest available version through the WordPress admin dashboard (Plugins > Add New > Upload or WP-Admin > Dashboard > Updates).
  3. 3. If automatic updates are enabled, ensure the plugin updates to a version higher than 3.2.5.
  4. 4. Verify the update was successful by checking the plugin version in Plugins list.
  5. 5. Test that the shortcode functionality still works as expected on your site.
Caveat Review changelog for any breaking changes between your current version and the new version; test in staging if possible

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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