CVE-2025-67919
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in WofficeIO Woffice Core woffice-core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Woffice Core: from n/a through <= 5.4.30.
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 confidenceAuthorization bypass vulnerability in Woffice Core WordPress plugin where user-controlled input (a key) allows attackers to bypass access control security levels due to incorrectly configured authorization logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm Woffice Core plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Woffice Core' in the list of active plugins.Affected if Woffice Core plugin is present and active in the WordPress installation
-
Identify installed Woffice Core versionIn the Plugins list, locate Woffice Core and view the version number displayed beneath the plugin name. Alternatively, check the plugin header in /wp-content/plugins/woffice-core/ folder for the 'Version' tag.Affected if Version is unknown or falls within any unpatched release range
-
Verify WordPress REST API or AJAX endpoints exposed by WofficeReview WordPress site for any publicly accessible AJAX actions or REST API endpoints that belong to Woffice. Check wp-content/plugins/woffice-core/ directory for ajax or api related PHP files. Look for endpoints that accept a user-supplied key parameter.Affected if Woffice exposes endpoints accepting key-based authentication without proper authorization validation
-
Check for unusual access patterns or unauthorized content accessReview server access logs for requests to Woffice-related endpoints containing unusual or unexpected key parameters. Look for requests to /wp-json/woffice/ or /wp-admin/admin-ajax.php?action=woffice* patterns.Affected if Logs show requests accessing protected content or admin functions using arbitrary key values without proper authorization failures
-
Inspect user role and capability configurationsIn WordPress admin, go to Users > Roles or any Woffice-specific role management. Verify that roles and capabilities are properly assigned and that no excessive permissions exist for lower-privileged users.Affected if Lower-privileged users can access content or functions reserved for higher roles through key-based bypass
A user is affected if Woffice Core plugin is installed and its authorization logic can be bypassed through user-supplied key parameters to access restricted content or functions.
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.
From vendor dataUpdate Woffice Core to the latest patched version. Review and harden access control configurations to ensure authorization checks cannot be bypassed through user-supplied keys or parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67919 — 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-2025-67919 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