dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10049

HIGH · 7.2 CVSS v3.1 Published 2025-09-10
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 Responsive Filterable Portfolio plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation via the HdnMediaSelection_image field in all versions up to, and including, 1.0.24. 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.

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 Responsive Filterable Portfolio WordPress plugin lacks file type validation on the HdnMediaSelection_image field, allowing authenticated administrators to upload arbitrary files to the server. This arbitrary file upload vulnerability can lead to remote code execution if malicious files (e.g., PHP scripts) are uploaded.

MitigationUpdate the plugin to version 1.0.25 or later which includes proper file type validation. Alternatively, restrict administrator-level access to trusted users only until the patch can be applied.

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. Confirm the plugin is installed
    Access WordPress admin > Plugins and check if Responsive Filterable Portfolio appears in the list of installed plugins
    Affected if The plugin is present and active in the WordPress installation
  2. Determine the installed version
    In WordPress admin > Plugins, find Responsive Filterable Portfolio and view the version number displayed beneath the plugin name, or read the version from the plugin's main PHP header
    Affected if The installed version is lower than 1.0.25
  3. Verify administrator accounts exist
    Access WordPress admin > Users and review the user roles to confirm whether any accounts have Administrator-level privileges, which is required to exploit this vulnerability
    Affected if There is at least one user with Administrator role
  4. Check if plugin settings are accessible
    Navigate to the plugin's admin interface (typically under Portfolio or a custom post type created by the plugin) where the HdnMediaSelection_image field would be used for media selection
    Affected if The plugin's media upload or portfolio settings interface is accessible

The environment is affected if Responsive Filterable Portfolio is installed with a version earlier than 1.0.25 and the WordPress site has administrator-level accounts that can access the plugin's upload functionality.

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 version 1.0.25 or later which includes proper file type validation. Alternatively, restrict administrator-level access to trusted users only until the patch can be applied.

Recommended fix Moderate confidence

1.0.25 or later

  1. 1. Log in to the WordPress admin dashboard with Administrator-level access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Responsive Filterable Portfolio' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/responsive-filterable-portfolio/
  6. 6. After updating, verify the new version number (should be 1.0.25 or higher) in the plugin details

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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