dbcve.org
WofficeWordPress extension · Xtendify

CVE-2024-43234

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-16
Fix available
A fix is available. Upgrade to 5.4.15 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
Authentication Bypass Using an Alternate Path or Channel vulnerability in WofficeIO Woffice woffice allows Authentication Bypass.This issue affects Woffice: from n/a through <= 5.4.14.

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 · moderate confidence

The Woffice plugin for WordPress contains an authentication bypass vulnerability allowing attackers to circumvent the normal login mechanism through an alternate path or channel. This critical flaw (CVSS 9.8) enables unauthenticated attackers to gain unauthorized access to the application, likely through a secondary authentication entry point or mechanism that fails to properly validate credentials.

MitigationUpgrade to the latest version of Woffice immediately. If no patched version is available, disable the plugin temporarily and review access logs for signs of exploitation. Audit authentication-related code for hardcoded credentials, backdoors, or insecure alternative authentication paths.

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.15

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. Verify Woffice plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Woffice' or 'Xtendify Woffice' in the list of installed plugins.
    Affected if Woffice plugin appears in the installed plugins list
  2. Check installed Woffice version
    In the WordPress admin under Plugins > Installed Plugins, locate the Woffice plugin entry. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (typically wp-content/plugins/woffice/woffice.php) and look for the 'Version' header in the plugin comments.
    Affected if Version displayed is below 5.4.15 (e.g., 5.4.14, 5.4.13, etc.)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the Woffice plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if Plugin status is Active - this means the authentication bypass vulnerability is exploitable
  4. Inspect authentication-related endpoints
    If you have access to server logs or a web application firewall, search for access attempts to WordPress login, XML-RPC, or REST API endpoints originating from unexpected sources or showing anomalous authentication patterns.
    Affected if Unusual or successful unauthenticated access patterns are observed in logs

Your environment is affected if the Woffice plugin is installed, active, and running a version lower than 5.4.15.

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.15 or later
Fixed in 5.4.15
Interim mitigation

Upgrade to the latest version of Woffice immediately. If no patched version is available, disable the plugin temporarily and review access logs for signs of exploitation. Audit authentication-related code for hardcoded credentials, backdoors, or insecure alternative authentication paths.

Recommended fix High confidence

5.4.15

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Woffice in the plugin list
  4. Check if an update is available and update to version 5.4.15 or latest available version
  5. Alternatively, update via WordPress updates page if auto-update is enabled
  6. Verify the installed version shows 5.4.15 or higher after update

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

Fix this in Woffice Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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