dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27435

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

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
Missing Authorization vulnerability in WofficeIO Woffice allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Woffice: from n/a before 5.4.33.

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

Missing authorization vulnerability in WofficeIO Woffice plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to certain functionalities or data that should require elevated privileges.

MitigationUpdate Woffice to version 5.4.33 or later which should contain proper authorization fixes, and conduct a comprehensive review of access control configurations throughout the plugin.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Identify Woffice plugin version
    Locate the Woffice plugin files in your WordPress installation (typically in wp-content/plugins/woffice) and check the main plugin file (usually main.php or readme.txt) for the version number, or access it via WordPress admin dashboard under Plugins > Installed Plugins
    Affected if The installed version is lower than 5.4.33
  2. Verify WordPress admin access
    Log into the WordPress admin dashboard and navigate to Woffice settings (usually under Woffice > Settings or similar) to review the access control configuration panel
    Affected if Settings pages are accessible without proper authentication or authorization checks are missing
  3. Inspect access control security levels
    Examine the Woffice plugin access control settings panel for any misconfigured security levels, particularly around user role permissions, file access restrictions, and API endpoint protections
    Affected if Security levels are incorrectly configured or allow privilege escalation
  4. Check for exposed administrative functions
    Review the Woffice plugin directory for AJAX handlers or admin-ajax.php endpoints registered by Woffice, and test whether they enforce proper capability checks before executing privileged operations
    Affected if Administrative functionalities can be accessed by lower-privileged users or unauthenticated actors
  5. Audit custom post type and taxonomy permissions
    If Woffice creates custom post types or taxonomies, verify that their archive and single view pages respect WordPress user capabilities and role-based access settings
    Affected if Content that should require elevated privileges is publicly accessible

A user is affected if the Woffice plugin version is below 5.4.33 or if access control security levels are misconfigured to allow unauthorized access to privileged functionalities

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Woffice to version 5.4.33 or later which should contain proper authorization fixes, and conduct a comprehensive review of access control configurations throughout the plugin.

Recommended fix Moderate confidence

Woffice version 5.4.33

  1. 1. Backup your Woffice installation and database before making any changes
  2. 2. Upgrade Woffice to version 5.4.33 or later to resolve the missing authorization vulnerability
  3. 3. After upgrading, verify that access control security levels are properly configured in the Woffice admin dashboard
  4. 4. Test that authorization controls are functioning correctly for all user roles
  5. 5. Review user permissions and access levels to ensure they align with your security requirements

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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