dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66076

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-02
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
Unauthenticated Broken Access Control in Woostify Sites Library <= 1.6.2 versions.

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

Unauthenticated Broken Access Control vulnerability in the Woostify Sites Library WordPress plugin affecting versions 1.6.2 and earlier. The vulnerability allows unauthenticated attackers to bypass access controls, likely accessing sensitive site library functionality or data without proper authorization.

MitigationUpdate the Woostify Sites Library plugin to a version newer than 1.6.2. If no patched version is available, consider disabling the plugin or implementing temporary firewall rules to restrict access until a fix is released.

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. Verify Woostify Sites Library plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Woostify Sites Library' in the list
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In the Plugins list, click on 'Woostify Sites Library' to view the plugin details, or check the plugin header in /wp-content/plugins/woostify-sites-library/woostify-sites-library.php for the 'Version' field
    Affected if A version number is displayed and is 1.6.2 or lower
  3. Confirm the vulnerability scope
    This vulnerability affects unauthenticated (non-logged-in) users. Check if the WordPress site has the Woostify Sites Library functionality exposed publicly via REST API endpoints or frontend pages that do not require authentication
    Affected if The site library features are accessible without login to unauthenticated users
  4. Review access control configuration
    Examine the plugin files in /wp-content/plugins/woostify-sites-library/ for AJAX handlers or REST API routes that lack capability checks or nonce verification for unauthenticated requests
    Affected if Public-facing endpoints exist without proper authorization checks

A WordPress installation with Woostify Sites Library plugin version 1.6.2 or earlier installed is potentially affected by this unauthenticated broken access control vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Woostify Sites Library plugin to a version newer than 1.6.2. If no patched version is available, consider disabling the plugin or implementing temporary firewall rules to restrict access until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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