CVE-2025-68069
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 wpWax Directorist directorist allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Directorist: from n/a through <= 8.6.6.
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 in wpWax Directorist plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability enables unauthorized access to certain functionalities or data due to missing capability checks or permission validations. This broken access control issue has a CVSS 7.1 indicating significant impact on confidentiality and integrity.
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
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Directorist plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Directorist' or check via wp-cli: wp plugin list --name='directorist'Affected if The Directorist plugin is present and active on the WordPress site
-
Identify installed Directorist versionCheck the plugin version in the plugin header (wp-content/plugins/directorist/readme.txt or composer.json) or via wp-cli: wp plugin get directorist --field=versionAffected if The installed version is unknown or unpatched (no specific vulnerable version range was provided, so compare to any available patched release)
-
Verify plugin is publicly accessibleTest if Directorist AJAX endpoints or admin pages are reachable without authentication: curl -s https://SITE/wp-admin/admin-ajax.php?action=directorist_[endpoint]Affected if The endpoint returns data or executes without requiring login or capability verification
-
Check for privilege escalation pathsSubmit requests as a low-privileged or logged-out user to Directorist endpoints that should require admin capabilities (e.g., settings, data export, user management endpoints)Affected if The system allows access or returns sensitive data without proper capability checks (manage_options, edit_users, etc.)
A user is affected if the Directorist plugin is installed and its endpoints/settings are accessible without proper authorization checks or capability verification.
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 (capability checks, nonce verification, role-based access control) on all sensitive endpoints and functionalities within the Directorist plugin. Update to the patched version once available.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68069 — 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-68069 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