CVE-2025-67975
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 aDirectory aDirectory adirectory allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects aDirectory: from n/a through <= 3.0.3.
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 the aDirectory WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before granting access to sensitive functionality, enabling unauthorized users to access resources or actions they should not be permitted to reach.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm aDirectory plugin is installedNavigate to WordPress admin > Plugins and verify aDirectory plugin appears in the installed plugins list. Note whether it is activated.Affected if aDirectory plugin is installed and activated on the WordPress site
-
Identify plugin versionIn Plugins list, click on aDirectory to view the plugin details popup or view the plugin main file header to determine the installed version number.Affected if Installed version matches or precedes the vulnerable version range (check against any published advisory)
-
Verify access control security level configurationGo to aDirectory settings page in WordPress admin > aDirectory > Settings. Locate any security level, access control, or permission-related configuration options. Check if the security level is set to a value that permits broader access than intended.Affected if Security level is set to a permissive value that could allow unauthorized access to sensitive functionality
-
Test for missing authorization on sensitive functionsUsing a low-privilege user account (subscriber or contributor role), attempt to access aDirectory administrative functions or endpoints that should require admin-level permissions. Compare actual access against expected access control policy.Affected if Low-privilege users can access administrative features or data they should not be able to reach
-
Audit user role and capability assignmentsNavigate to WordPress Users > Roles or use a role management plugin to review what capabilities are assigned to each user role. Verify if aDirectory has added elevated capabilities to non-administrator roles.Affected if Non-administrator roles possess capabilities that should be restricted to administrators
The site is affected if aDirectory plugin is installed, any user with insufficient privileges can access restricted functionality due to missing authorization checks, or the security level configuration permits unintended access.
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 at all access control boundaries and update to any patched version when available. Until a patch is released, restrict administrative access to trusted users and audit all user role configurations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67975 — 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-67975 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