dbcve.org
WofficeWordPress extension · Xtendify

CVE-2025-7694

HIGH · 7.5 CVSS v3.1 Published 2025-08-02
Fix available
A fix is available. Upgrade to 5.4.27 or later.
See remediation →
81/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 Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the woffice_file_manager_delete() function in all versions up to, and including, 5.4.26. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 contains an arbitrary file deletion vulnerability in the woffice_file_manager_delete() function. Insufficient validation of file path inputs allows authenticated users with Contributor-level permissions or higher to delete arbitrary files on the server by manipulating the file path parameter, potentially leading to remote code execution if critical files like wp-config.php are targeted.

MitigationUpgrade to Woffice Core version 5.4.27 or later which contains the patch. Alternatively, disable the file manager functionality or restrict user permissions 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.27

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Verify Woffice plugin is installed
    Navigate to WordPress Admin > Plugins and check if 'Woffice Core' (or 'Xtendify Woffice') appears in the installed plugins list
    Affected if Woffice Core plugin is not installed on the WordPress site
  2. Check installed Woffice version
    In WordPress Admin > Plugins, locate Woffice Core and view the version number displayed beneath the plugin name, or check the plugin header in /wp-content/plugins/woffice-core/woffice.php for the 'Version' tag
    Affected if The installed version is any version earlier than 5.4.27 (e.g., 5.4.26, 5.4.0, etc.)
  3. Confirm file manager functionality is accessible
    Attempt to access the file manager feature in Woffice (typically found in the WordPress admin under Woffice settings or a file manager menu item), or check if the woffice_file_manager_delete() function exists in the codebase at /wp-content/plugins/woffice-core/
    Affected if The file manager module is enabled and accessible to users
  4. Check for Contributor-level or higher users
    In WordPress Admin > Users, review the user list to identify any accounts assigned the Contributor, Author, Editor, or Administrator role
    Affected if There exists at least one user with Contributor-level permissions or higher who could potentially trigger the vulnerable function

A site is affected if Woffice Core version is below 5.4.27, the file manager feature is enabled, and at least one user with Contributor-level permissions or higher exists 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
Upgrade available Upgrade to 5.4.27 or later
Fixed in 5.4.27
Interim mitigation

Upgrade to Woffice Core version 5.4.27 or later which contains the patch. Alternatively, disable the file manager functionality or restrict user permissions until the patch can be applied.

Recommended fix High confidence

Woffice Core plugin version 5.4.27

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'Woffice Core' plugin in the plugin list.
  4. 4. If an update is available, click 'Update Now' to update to version 5.4.27 or later.
  5. 5. Alternatively, download version 5.4.27 from the official Woffice source (hub.woffice.io or themeforest.net) and upload/install it via WordPress plugin upload.
  6. 6. After updating, verify the plugin version shows 5.4.27 or higher in the plugins list.
  7. 7. Test that the file manager functionality still works correctly with legitimate files.

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

Fix this in Woffice 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 the upgrade done

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