dbcve.org
WofficeWordPress extension · Xtendify

CVE-2025-2797

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to 5.4.22 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Cross-Site Request Forgery in all versions up to, and including, 5.4.21. This is due to missing or incorrect nonce validation on the 'woffice_handle_user_approval_actions' function. This makes it possible for unauthenticated attackers to approve registration for any user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 fails to validate nonces in the 'woffice_handle_user_approval_actions' function, allowing unauthenticated attackers to forge administrative requests. By tricking an admin into clicking a malicious link, attackers can approve user registrations without valid authentication credentials.

MitigationAdd proper nonce validation using wp_verify_nonce() or check_admin_referer() to the 'woffice_handle_user_approval_actions' function to ensure requests originate from legitimate admin sessions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Woffice Core' by Xtendify, or inspect the main plugin file (usually /wp-content/plugins/woffice-core/woffice-core.php) to find the version header.
    Affected if Woffice Core plugin is not installed or not found in the system.
  2. Compare installed version against vulnerable range
    Read the version number from the plugin header identified in step 1 and compare it to 5.4.22. Versions below 5.4.22 (e.g., 5.4.21, 5.4.0, 4.x.x) are in the vulnerable range.
    Affected if Installed version is lower than 5.4.22.
  3. Locate the vulnerable function
    Search the plugin files for the function 'woffice_handle_user_approval_actions'. This is typically found in the main plugin file or an includes file handling user approval functionality.
    Affected if The function woffice_handle_user_approval_actions is not found in the codebase.
  4. Inspect function for nonce validation
    Open the file containing woffice_handle_user_approval_actions and examine the function body. Look for calls to wp_verify_nonce(), check_admin_referer(), or wp_nonce_verify() at the beginning of the function before any approval actions are processed.
    Affected if The function exists but contains NO nonce validation (no wp_verify_nonce, check_admin_referer, or wp_nonce_verify calls) at the start of the function.

You are affected if Woffice Core plugin version is below 5.4.22 AND the woffice_handle_user_approval_actions function exists without nonce verification logic.

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

Add proper nonce validation using wp_verify_nonce() or check_admin_referer() to the 'woffice_handle_user_approval_actions' function to ensure requests originate from legitimate admin sessions.

Recommended fix High confidence

Woffice Core plugin version 5.4.22

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the Woffice Core plugin and check the current version to confirm it is below 5.4.22
  4. Update the Woffice Core plugin to version 5.4.22 or later via the WordPress plugin updates interface
  5. Verify the update was successful by confirming the plugin version now shows 5.4.22 or higher
  6. Test the user approval functionality to ensure the plugin continues to work correctly after the update
Caveat Standard security patch with no expected breaking changes; always test in a staging environment first

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

Fix this in Woffice Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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