dbcve.org
DroipWordPress extension · Themeum

CVE-2025-5831

HIGH · 8.8 CVSS v3.1 Published 2025-07-25
Fix available
A fix is available. Upgrade to after 2.2.0 or later.
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 Droip plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the make_google_font_offline() function in all versions up to, and excluding, 2.5.2. This makes it possible for authenticated attackers, with Subscriber-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 Droip WordPress plugin contains an arbitrary file upload vulnerability in the make_google_font_offline() function. Authenticated users with Subscriber-level access can upload arbitrary files to the server due to missing file type validation, potentially achieving remote code execution.

MitigationUpdate the Droip plugin to version 2.5.2 or later which includes proper file type validation. If immediate update is not possible, consider restricting user uploads or temporarily disabling the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DroipWordPress extension
Affected:<= 2.2.0

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 Droip plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Themeum Droip' or 'Droip'. Alternatively, check the /wp-content/plugins/droip/ directory exists on the server.
    Affected if The Droip plugin is found installed on the WordPress site
  2. Identify installed Droip version
    Check the plugin main file (droip.php) for the 'Version' header, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'droip_version'
    Affected if The installed version is 2.2.0 or lower (any version <= 2.2.0)
  3. Verify subscriber-level accounts exist
    Navigate to Users > All Users in WordPress admin and review user roles. Or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities'
    Affected if Any user account has Subscriber role or higher is present on the site
  4. Check if make_google_font_offline endpoint is accessible
    Inspect plugin AJAX handlers in droip.php or related files for 'make_google_font_offline' action hook. Test by checking if the endpoint /wp-admin/admin-ajax.php?action=make_google_font_offline responds.
    Affected if The endpoint is present and responds without requiring higher privileges than Subscriber
  5. Review user upload capabilities
    Check if the site allows user registrations and if the default role for new users permits file uploads. Examine WordPress settings under Settings > General > New User Default Role.
    Affected if New user registration is enabled with Subscriber (or higher) as the default role

If Droip plugin version is 2.2.0 or lower AND any subscriber-level user account exists on the site, the vulnerability is present and exploitable.

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
Upgrade available Upgrade to a release after 2.2.0
Interim mitigation

Update the Droip plugin to version 2.5.2 or later which includes proper file type validation. If immediate update is not possible, consider restricting user uploads or temporarily disabling the plugin.

Recommended fix High confidence

2.5.2

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Droip plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.5.2 or higher
  5. 5. Verify the update was successful by checking the plugin version

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

Fix this in Droip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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