CVE-2025-67566
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 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 confidenceMissing authorization vulnerability in Woffice Core allows users to access functionality without proper authentication or with insufficient permissions. The access control security levels are incorrectly configured, potentially allowing unauthorized access to sensitive features or data that should require higher privilege levels.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installationIdentify if the Woffice theme or plugin is present in your WordPress environment by checking the theme folder or plugin directory for Woffice-related filesAffected if Woffice Core is installed and the version falls within the affected range (if version info is available)
-
Determine installed Woffice versionLocate the version information in the theme style.css header, plugin main file, or version definition file. Compare against any known affected version ranges provided by official sourcesAffected if The installed version matches or falls within the vulnerable version range
-
Review user role and capability settingsNavigate to WordPress user management and Woffice-specific role configuration areas. Check if lower-privileged roles (subscriber, contributor, editor) have been granted capabilities that should be restricted to administrators onlyAffected if Non-admin users have access to administrative capabilities or functions
-
Test access to sensitive endpointsAttempt to access Woffice admin-sensitive features, settings pages, or user management functions while logged in as a low-privilege user. Observe whether the application enforces authorization checksAffected if Lower-privileged users can access features that should require administrator-level permissions
-
Inspect access control configuration filesReview Woffice Core configuration files for access control settings, permission definitions, or security level configurations. Look for roles configuration, capability maps, or authorization rulesAffected if Access control settings are missing, misconfigured, or allow unauthorized access to privileged functions
You are affected if Woffice Core is installed and users with insufficient privileges can access administrative or sensitive functionality that should require higher authorization levels.
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 dataImplement proper authorization checks on all sensitive endpoints and functions to verify user permissions before granting access. Review and correct the access control security level configurations to ensure proper segregation of privileges.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67566 — 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-67566 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