dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-4413

HIGH · 8.8 CVSS v3.1 Published 2025-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The Pixabay Images plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the pixabay_upload function in all versions up to, and including, 3.4. This makes it possible for authenticated attackers, with Author-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 Pixabay Images WordPress plugin lacks proper file type validation in its pixabay_upload function, allowing authenticated users with Author-level access or higher to upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the plugin to a version beyond 3.4 if available; if no patch exists, disable or remove the plugin until proper file type and extension validation can be implemented in the upload function.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Pixabay Images plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Pixabay Images' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'pixabay-images' or similar.
    Affected if The plugin is present in the plugins directory regardless of activation status
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Pixabay Images, and note the version number displayed below the plugin name. If not visible in admin, check the main plugin PHP file header for 'Version:' field or check the plugin's readme.txt file.
    Affected if The installed version is 3.4 or lower (the vulnerability affects versions up to and including 3.4)
  3. Verify user role configuration
    Navigate to Users > All Users in WordPress admin. Review the list to identify any users with Author, Editor, or Administrator roles, as these roles meet the minimum privilege requirement for exploitation.
    Affected if At least one user with Author-level or higher access exists on the site
  4. Inspect upload directory for suspicious files
    Check the WordPress uploads directory (typically /wp-content/uploads/) and its subdirectories for file extensions that are unusual for image uploads, such as .php, .phtml, .exe, .js, or .htaccess. Use file system commands or FTP to list and examine recent files.
    Affected if Unexpected executable or script files are present in the uploads folder, especially if they were uploaded recently and do not belong to other known plugins or themes

The environment is affected if the Pixabay Images plugin version is 3.4 or lower and the plugin is installed, especially when users with Author-level or higher privileges exist on the site.

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 a version beyond 3.4 if available; if no patch exists, disable or remove the plugin until proper file type and extension validation can be implemented in the upload function.

Recommended fix Moderate confidence

Version 3.5 or later

  1. 1. Log in to the WordPress admin dashboard with Author-level access or higher
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Pixabay Images plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.5 or later
  5. 5. Verify the update completed successfully
  6. 6. Confirm the new version number in the plugins list

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-4413 — 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-4413 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