dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-32652

CRITICAL · 9.9 CVSS v3.1 Published 2025-04-17
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 solacewp Solace Extra solace-extra allows Using Malicious Files.This issue affects Solace Extra: from n/a through <= 1.3.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 · moderate confidence

The Solace Extra plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) in version 1.3.1 and below, allowing attackers to upload dangerous file types without proper validation. The critical CVSS 9.9 score indicates severe impact, likely including potential remote code execution if malicious PHP or other executable files can be uploaded and accessed.

MitigationRestrict file uploads by implementing strict allowlist-based file type validation, storing uploads outside the web root, renaming uploaded files, and disabling script execution in upload directories. Update to any available patched version immediately.

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. Confirm Solace Extra plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'solace-extra' or similar.
    Affected if The Solace Extra plugin appears in the installed plugins list or plugin directory.
  2. Identify installed version
    Open the main plugin file (typically plugin-name.php) in the Solace Extra plugin folder and locate the version comment or header information, or check the plugin details displayed in the WordPress plugins admin page.
    Affected if The version is 1.3.1 or any version lower (e.g., 1.3.0, 1.2.x, 1.1.x, 1.0.x).
  3. Verify file upload functionality exists
    Search the plugin source code for file upload handling functions (move_uploaded_file, wp_handle_upload, $_FILES references) or locate any settings page that enables or configures file uploads.
    Affected if The plugin includes file upload handling code and this feature is accessible or enabled on the site.
  4. Inspect upload directories for suspicious files
    Check the wp-content/uploads/ directory (and any custom upload paths configured in the plugin) for unexpected file types such as .php, .phtml, .phar, .exe, or scripts with double extensions (e.g., file.php.jpg).
    Affected if Executable or potentially malicious file types are present in upload directories, especially in web-accessible locations.
  5. Check script execution restrictions
    Examine .htaccess files in upload directories and server configuration for directives that disable script execution (e.g., 'SetHandler None' or 'php_flag engine off'), or verify uploads are stored outside the web root.
    Affected if No script execution restrictions are in place and uploads remain within the web-accessible directory structure.

If Solace Extra plugin version 1.3.1 or below is installed with file upload functionality enabled and no script execution restrictions exist on upload directories, the environment is vulnerable to CVE-2025-32652.

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 by implementing strict allowlist-based file type validation, storing uploads outside the web root, renaming uploaded files, and disabling script execution in upload directories. Update to any available patched version immediately.

Recommended fix Low confidence

Latest version beyond 1.3.1 (check WordPress plugin repository for current stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Solace Extra' (solace-extra) in the plugin list
  4. If an update is available, click 'Update Now' to install the latest patched version
  5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running on a version greater than 1.3.1
  7. Test file upload functionality to confirm the restriction is properly enforced

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-2025-32652 — 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-32652 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