dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-24379

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Authorization Bypass Through User-Controlled Key vulnerability in wpjobportal WP Job Portal wp-job-portal allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Job Portal: from n/a through <= 2.4.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 confidence

Authorization bypass through user-controlled key vulnerability in WP Job Portal plugin <= 2.4.3 allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to resources or actions beyond the user's intended privileges.

MitigationUpdate WP Job Portal to the latest version and audit all endpoints to ensure proper authorization checks are enforced before allowing access to sensitive operations.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 WP Job Portal plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP Job Portal' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-job-portal' or similar.
    Affected if The WP Job Portal plugin is found in the WordPress installation
  2. Check installed WP Job Portal version
    In WordPress admin, click on the WP Job Portal plugin to view its details, or open the main plugin file (typically wp-job-portal.php) and look for the 'Version:' header comment. Compare the version number against <=2.4.3.
    Affected if The installed version is 2.4.3 or any earlier version
  3. Identify access control security level configuration
    Navigate to WP Job Portal settings in WordPress admin. Look for configuration options related to security levels, access control, or user permissions. Check for any settings that allow user-controlled keys or role-based access controls.
    Affected if Security level settings are configured to allow user-controlled keys or overly permissive access beyond intended privileges
  4. Review endpoint access permissions
    Test access to sensitive WP Job Portal endpoints (job applications, resume manager, job listings) using accounts with different privilege levels. Attempt actions that should be restricted based on user role.
    Affected if Lower-privileged users can access or modify resources belonging to higher-privileged users or perform actions outside their intended permissions

A user is affected if WP Job Portal version 2.4.3 or earlier is installed AND the access control security levels are misconfigured to allow privilege escalation through user-controlled keys.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Job Portal to the latest version and audit all endpoints to ensure proper authorization checks are enforced before allowing access to sensitive operations.

Recommended fix Moderate confidence

latest stable version of WP Job Portal (wp-job-portal) plugin (version > 2.4.3)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WP Job Portal (wp-job-portal) in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is working correctly by testing job posting and application submission functionality
  6. 6. Check the plugin's changelog or the WordPress plugin repository for any security-related release notes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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