dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-3234

HIGH · 7.2 CVSS v3.1 Published 2025-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 File Manager Pro – Filester plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 1.8.8. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. Administrators have the ability to extend file manager usage privileges to lower-level users including subscribers, which would make this vulnerability more severe on such sites.

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 File Manager Pro – Filester WordPress plugin up to version 1.8.8 lacks proper file type validation in its file upload functionality, allowing authenticated administrators to upload arbitrary files to the server, potentially leading to remote code execution.

MitigationUpdate the plugin to the latest version which implements proper file type validation and restricts dangerous file extensions. If unable to update immediately, restrict the file manager permissions to only trusted administrators and consider disabling the plugin.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 Filester plugin is installed
    Check for the plugin directory at wp-content/plugins/filester/ or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The Filester plugin directory exists in wp-content/plugins/filester/
  2. Identify installed plugin version
    Open the main plugin file (filester/filester.php) and locate the version comment in the file header, or check the version column in WordPress admin Plugins page
    Affected if The version listed is 1.8.8 or lower
  3. Confirm file manager functionality is active
    Check if the Filester plugin is activated in WordPress admin under Plugins > Installed Plugins, and verify the File Manager menu item appears in the admin sidebar
    Affected if The plugin shows as Active and the File Manager menu is visible in the admin dashboard
  4. Inspect upload directory for anomalous files
    Navigate to the WordPress uploads directory (typically wp-content/uploads/) and review file types, particularly looking for executable extensions such as .php, .phtml, .php5, .js, or .sh in unexpected locations
    Affected if Unexpected executable files are present in upload directories that were not intentionally uploaded through legitimate WordPress media functions

You are affected if the Filester plugin is installed, shows version 1.8.8 or lower, is currently activated, and contains unexpected executable files in upload directories.

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 the plugin to the latest version which implements proper file type validation and restricts dangerous file extensions. If unable to update immediately, restrict the file manager permissions to only trusted administrators and consider disabling the plugin.

Recommended fix Moderate confidence

Version 1.8.9 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'File Manager Pro – Filester' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.8.9 or later from the WordPress plugin repository
  5. Verify the plugin is updated to version 1.8.9 or higher
  6. Confirm the update was successful by checking the plugin version number

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