CVE-2025-67967
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 e-plugins Lawyer Directory lawyer-directory allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Lawyer Directory: from n/a through <= 1.3.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 confidenceThe Lawyer Directory plugin for WordPress (versions <= 1.3.3) contains a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This IDOR or privilege escalation issue permits unauthorized users to access administrative functions or sensitive 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Check Lawyer Directory plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Lawyer Directory', or check the plugin's main PHP file for the 'Version' header in the plugin comment blockAffected if The installed version is 1.3.3 or lower
-
Verify plugin is activeConfirm the Lawyer Directory plugin is currently activated in the WordPress plugins listAffected if The plugin is active and the version is vulnerable
-
Inspect admin functions for capability checksExamine the plugin's PHP files (especially in /admin or /includes folders) for sensitive functions like settings, user management, or data export. Look for missing current_user_can() or similar authorization checks before privileged operationsAffected if Admin or privileged functions lack proper capability verification before execution
-
Check for exposed AJAX or REST endpointsReview the plugin for wp_ajax_ and wp_ajax_nopriv_ hooks that may allow unauthenticated or low-privilege users to trigger privileged actionsAffected if The plugin registers AJAX or REST endpoints accessible without proper authorization checks
-
Test access control with low-privilege accountCreate or use a subscriber-level user account and attempt to access plugin admin pages or trigger plugin administrative actions directly via URL or APIAffected if A low-privilege user can access administrative functions or sensitive data they should not be able to reach
You are affected if the Lawyer Directory plugin version is 1.3.3 or lower AND sensitive plugin functions can be accessed or executed by unauthorized users without proper 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 dataUpdate to the latest patched version of the Lawyer Directory plugin. If no patch is available, audit the plugin code for all sensitive functions and implement proper capability checks (e.g., current_user_can()) before executing privileged operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67967 — 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-67967 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