CVE-2026-25404
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 Automattic WP Job Manager wp-job-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Job Manager: from n/a through <= 2.4.0.
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 WP Job Manager plugin allows attackers to bypass access controls due to incorrectly configured security levels. The flaw enables unauthorized access to functionality that should be restricted to privileged users.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify WP Job Manager is installedNavigate to WordPress Admin > Plugins and confirm WP Job Manager is active, or check the plugin files in /wp-content/plugins/wp-job-manager/ for the main plugin file and read the version headerAffected if The plugin is installed and active
-
Identify installed versionCheck the plugin version number in the plugin header of wp-job-manager.php or in the WordPress plugin admin pageAffected if Version is within the affected range (compare to the specific vulnerable version noted in CVE-2026-25404)
-
Test for authorization bypass on sensitive endpointsUse a non-privileged user account (subscriber role) to access typical admin-only functions such as job submission management, applicant data, or plugin settings pages via direct URL access without receiving proper authorization errorsAffected if Non-privileged users can access functionality restricted to administrators or privileged roles
-
Inspect role capability configurationExamine the plugin source code in includes/class-wp-job-manager-roles.php or related capability files to verify if proper capability checks (like manage_options or view_admin) are enforced before executing sensitive operationsAffected if Sensitive functions lack proper capability checks or use weak/incorrect role validation
-
Check AJAX actions for authorizationReview AJAX endpoints exposed by the plugin (in admin-ajax.php calls from wp-job-manager) and test whether actions like creating/editing jobs, accessing applicant data, or modifying settings work without authentication or with low-privileged user sessionsAffected if AJAX actions execute sensitive operations without verifying user capabilities
Your environment is affected if WP Job Manager is installed and non-privileged users can access admin-level functionality without proper authorization checks.
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 role-based access control (RBAC) checks and authorization validation for all sensitive operations in the plugin.
- 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-2026-25404 — 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-2026-25404 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