dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-69312

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-22
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 Xpro Xpro Elementor Addons xpro-elementor-addons allows Upload a Web Shell to a Web Server.This issue affects Xpro Elementor Addons: from n/a through <= 1.4.19.1.

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 Xpro Elementor Addons plugin before version 1.4.19.1 contains an unrestricted file upload vulnerability that allows authenticated or unauthenticated attackers to upload dangerous file types (such as PHP scripts) to the web server. Attackers can then execute these web shells to achieve remote code execution and potentially gain full control of the affected website.

MitigationImmediately disable or remove the vulnerable plugin until a patched version (1.4.20 or higher) can be installed. If the plugin must remain active, implement strict server-side file type validation, restrict upload directories to non-executable locations, and disable script execution in upload directories.

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 Xpro Elementor Addons plugin is installed
    Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory on the server for a folder named 'xpro-elementor-addons' or similar
    Affected if The plugin folder exists on the server
  2. Determine the installed version number
    In the WordPress Plugins list, find the Xpro Elementor Addons entry and read the version number displayed under the plugin name, or open the main plugin PHP file and locate the 'Version:' header in the file comments
    Affected if The installed version is 1.4.19.1 or lower
  3. Identify if file upload features are in use
    Review the website for any frontend forms, widgets, or post types created with this plugin that include file upload fields, or check the plugin settings for enabled upload-related widgets
    Affected if Any Xpro file upload widget or form is active on the site
  4. Check upload directory script execution status
    Inspect the server configuration for the uploads directory (typically /wp-content/uploads) and verify if .php or script execution is permitted within that path
    Affected if The upload directory allows execution of uploaded PHP files

If the plugin is installed with version 1.4.19.1 or earlier and any file upload functionality from this plugin is accessible, the environment is affected by this vulnerability

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 disable or remove the vulnerable plugin until a patched version (1.4.20 or higher) can be installed. If the plugin must remain active, implement strict server-side file type validation, restrict upload directories to non-executable locations, and disable script execution in upload directories.

Recommended fix Moderate confidence

Upgrade to the latest version of Xpro Elementor Addons (version 1.4.20 or higher if available)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Xpro Elementor Addons' in the plugin list
  4. 4. Check the current version number displayed under the plugin name
  5. 5. If the installed version is 1.4.19.1 or lower, update the plugin to the latest available version
  6. 6. After updating, verify the new version is installed successfully
  7. 7. Test file upload functionality to ensure the plugin still works correctly after the update
Caveat Standard plugin update - review plugin settings after upgrade as minor configuration changes may occur

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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