WofficeWordPress extension · Xtendify
CVE-2024-37470
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 · uneditedMissing Authorization vulnerability in WofficeIO Woffice Core allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Woffice Core: from n/a through 5.4.8.
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 confidenceWoffice Core plugin versions up to 5.4.8 contain a missing authorization vulnerability (CWE-862) where certain functionality is not properly constrained by access control lists, allowing unauthenticated or unauthorized users to access sensitive features that should require proper authentication and authorization checks.
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
< 5.4.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Woffice Core plugin versionLocate the Woffice Core plugin file (typically in wp-content/plugins/woffice-core or similar) and check the main plugin file header for the Version field, or access it via WordPress admin plugin listAffected if The installed version is 5.4.8 or lower (any version below 5.4.9)
-
Verify sensitive endpoint accessibilityTest access to sensitive Woffice features or AJAX actions without authentication using a tool like Burp Suite or curl - attempt requests to common Woffice AJAX endpoints (such as wp-admin/admin-ajax.php actions related to user data, projects, or directory) without valid credentialsAffected if Requests to sensitive functionality return successful responses instead of requiring authentication or returning 401/403 errors
-
Inspect authorization logic in plugin codeReview Woffice Core plugin files for access control checks - examine PHP files in the plugin directory for function calls that verify user capabilities (current_user_can, wp_verify_nonce, etc.) around sensitive operations like user data retrieval, project management, or administrative functionsAffected if Sensitive functions lack proper capability checks or nonce validation before executing privileged operations
-
Check for unauthenticated API exposureEnumerate and test public-facing Woffice API endpoints or AJAX actions - make HTTP requests to admin-ajax.php with various Woffice-specific actions while unauthenticated, observing whether data is returned without session authenticationAffected if API responses contain user data, project information, or administrative content without requiring authentication tokens or valid user sessions
A user is affected if the installed Woffice Core plugin version is below 5.4.9 AND sensitive endpoints/functions are accessible without proper authentication or authorization validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.4.9
Upgrade Woffice Core to the latest version which includes proper authorization checks, or implement role-based access control (RBAC) validation on all sensitive functions and API endpoints.
5.4.9
- Backup your WordPress site and database before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find Woffice in the plugin list and click 'Update now' to update to version 5.4.9
- Alternatively, go to Plugins > Add New > Upload and upload the Woffice 5.4.9 zip file
- Verify the update was successful by checking the Woffice version number in Plugins > Installed Plugins
- Clear any caching plugins or server-side caches after the update
- Test that the plugin functionality works correctly after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woffice
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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