dbcve.org
WofficeWordPress extension · Xtendify

CVE-2025-2798

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to 5.4.22 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 CRM theme for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.4.21. This is due to a misconfiguration of excluded roles during registration. This makes it possible for unauthenticated attackers to register with an Administrator role if a custom login form is being used. This can be combined with CVE-2025-2797 to bypass the user approval process if an Administrator can be tricked into taking an action such as clicking 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 CRM theme for WordPress contains a critical authentication bypass vulnerability (CVSS 9.8) in all versions up to 5.4.21. The flaw stems from a misconfiguration in the role exclusion logic during user registration, allowing unauthenticated attackers to register directly with Administrator privileges when a custom login form is deployed. This can be chained with CVE-2025-2797 to bypass any user approval workflow.

MitigationUpdate Woffice CRM theme to version 5.4.22 or later to patch the role misconfiguration. As an immediate step, disable custom login forms, audit all administrator accounts for unauthorized access, and review user registration logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Woffice theme version
    In WordPress admin, go to Appearance > Themes and locate Woffice. The version number is displayed on the theme card. Alternatively, check the style.css file in wp-content/themes/woffice/ for the 'Version:' comment header.
    Affected if Version is lower than 5.4.22 (for example, 5.4.21, 5.4.20, etc.)
  2. Verify if user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked. Then check if a custom login/registration form shortcode (such as [woffice_login] or [woffice_register]) is present on a page, or if a plugin like Woffice Login/Registration is configured to allow public registration.
    Affected if Anyone can register is enabled AND a custom Woffice login/registration form is in use on the site
  3. Inspect Administrator accounts for legitimacy
    In WordPress admin, go to Users > All Users. Review every account with the Administrator role. For each, verify the email address and creation date by clicking the username to view details. Cross-reference the creation date with known internal users and IT records.
    Affected if There exists an Administrator account that was not created by a known internal administrator, or the account email does not match your organization's domain or known users
  4. Check for recently created high-privilege accounts
    In WordPress admin, go to Users > All Users. Sort by 'Registered' column if available, or query the wp_users table directly: SELECT ID, user_login, user_email, user_registered FROM wp_users WHERE user_registered > DATE_SUB(NOW(), INTERVAL 30 DAY). Cross-reference creation times with your internal activity logs.
    Affected if Any Administrator-level account was registered within the past 30 days and you did not create it yourself

You are affected if Woffice version is below 5.4.22, user registration is enabled with a custom login form, AND there are unauthorized Administrator accounts in your WordPress users table.

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 CRM theme to version 5.4.22 or later to patch the role misconfiguration. As an immediate step, disable custom login forms, audit all administrator accounts for unauthorized access, and review user registration logs for signs of exploitation.

Recommended fix High confidence

Woffice 5.4.22

  1. Backup your WordPress site before making any changes
  2. Update the Woffice theme to version 5.4.22
  3. Verify the update was successful by checking the theme version in WordPress admin

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

Fix this in Woffice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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