dbcve.org
WofficeWordPress extension · Xtendify

CVE-2025-2780

HIGH · 8.8 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to 5.4.22 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 Woffice Core plugin for WordPress, used by the Woffice Theme, is vulnerable to arbitrary file uploads due to missing file type validation in the 'saveFeaturedImage' function in all versions up to, and including, 5.4.21. 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 Woffice Core WordPress plugin has an arbitrary file upload vulnerability in the 'saveFeaturedImage' function due to missing file type validation, allowing authenticated users with Subscriber-level permissions to upload arbitrary files to the server, potentially leading to remote code execution.

MitigationUpdate Woffice Core to version 5.4.22 or later which includes proper file type validation; if immediate patching is not possible, disable file upload functionality or restrict user capabilities 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.

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
WofficeWordPress extension
Affected:< 5.4.22

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 Woffice plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Woffice Core' in the installed plugins list, or check the /wp-content/plugins/woffice-core directory exists on the server
    Affected if The Woffice Core plugin is present on the WordPress site
  2. Identify installed Woffice version
    In WordPress Admin > Plugins, click on the Woffice Core plugin to view the version number, or read the main plugin file header (e.g., main.php or index.php in /wp-content/plugins/woffice-core/) for the 'Version' tag
    Affected if The installed version is earlier than 5.4.22 (e.g., 5.4.21, 5.4.20, etc.)
  3. Check for subscriber-level user accounts
    In WordPress Admin > Users, review the user list to see if any accounts have the 'Subscriber' role, or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'
    Affected if Any Subscriber-level user accounts exist on the site
  4. Verify file upload endpoint accessibility
    Check if the saveFeaturedImage AJAX action is registered and accessible by examining /wp-content/plugins/woffice-core/includes/ajax.php or similar files, and confirm non-admin users can access it
    Affected if The saveFeaturedImage function handles requests without verifying user administrative privileges or file type validation
  5. Inspect upload directory permissions
    Check if the /wp-content/uploads/woffice/ or similar upload directories are writable by the web server user (ls -la or file manager inspection)
    Affected if The upload directory is writable, allowing arbitrary files to be stored and potentially executed

A site is affected if Woffice Core version is below 5.4.22 AND at least one Subscriber-level user account exists AND the file upload functionality is accessible to that user role.

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 5.4.22 or later
Fixed in 5.4.22
Interim mitigation

Update Woffice Core to version 5.4.22 or later which includes proper file type validation; if immediate patching is not possible, disable file upload functionality or restrict user capabilities until the patch can be applied.

Recommended fix High confidence

Woffice version 5.4.22

  1. Upgrade the Woffice Core plugin or Woffice Theme to version 5.4.22 or later
  2. After upgrading, verify that the 'saveFeaturedImage' function now properly validates file types before allowing uploads
  3. Test the file upload functionality with a subscriber-level account to confirm the vulnerability is remediated
  4. Ensure that the uploaded files are stored in a non-executable directory and that uploaded files cannot be accessed directly as scripts
Caveat Review the Woffice 5.4.22 release notes for any theme/plugin compatibility changes before upgrading in production environments

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

Fix this in Woffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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