dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-4758

HIGH · 8.8 CVSS v3.1 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The WP Job Portal plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'WPJOBPORTALcustomfields::removeFileCustom' function in all versions up to, and including, 2.4.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 · high confidence

The WP Job Portal WordPress plugin up to version 2.4.9 contains an arbitrary file deletion vulnerability in the WPJOBPORTALcustomfields::removeFileCustom function. Due to insufficient file path validation, any authenticated user with Subscriber-level access can supply a crafted file path (including path traversal sequences or absolute paths) to delete arbitrary files on the server filesystem. Deletion of sensitive files like wp-config.php enables full site compromise and remote code execution.

MitigationUpdate the WP Job Portal plugin to the latest patched version. If no patch is available, implement strict whitelist-based path validation in the removeFileCustom function to ensure only files within allowed upload directories can be deleted, and disable the function for low-privilege users until patched.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Job Portal' in the list
    Affected if The WP Job Portal plugin is active and installed with version 2.4.9 or earlier
  2. Check installed plugin version
    Click on the WP Job Portal plugin in the Plugins list to view the version number, or inspect the plugin header in /wp-content/plugins/wp-job-portal/ folder
    Affected if Version is 2.4.9 or lower (any version up to and including 2.4.9 is affected)
  3. Confirm user registration is enabled
    Go to WordPress Settings > General > Membership and check 'Anyone can register' is selected, or query the 'users_can_register' option in wp_options table
    Affected if User registration is enabled, allowing potential attackers to create subscriber accounts
  4. Check for subscriber-level user accounts
    Go to Users > All Users in WordPress admin and look for users with 'Subscriber' role, or query wp_users and wp_usermeta for user_level 0 or subscriber role
    Affected if Any subscriber-level user accounts exist in the system
  5. Verify the removeFileCustom function is accessible
    Inspect the file /wp-content/plugins/wp-job-portal/includes/classes/customfields.php (or similar path) for the removeFileCustom function and confirm it lacks proper path validation using realpath() or similar checks
    Affected if The function exists and does not validate that the file path is within an allowed directory before deletion

A user is affected if WP Job Portal version 2.4.9 or earlier is installed AND user registration is enabled or subscriber accounts exist, allowing authenticated users to delete arbitrary files via the removeFileCustom function.

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 the WP Job Portal plugin to the latest patched version. If no patch is available, implement strict whitelist-based path validation in the removeFileCustom function to ensure only files within allowed upload directories can be deleted, and disable the function for low-privilege users until patched.

Recommended fix Moderate confidence

2.5.0 or later (check WordPress plugin repository for latest patched version)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the WP Job Portal plugin in the list.
  4. 4. Check the current installed version (if it's 2.4.9 or lower, the site is vulnerable).
  5. 5. If an update is available, click 'Update Now' to install the latest version that contains the security fix.
  6. 6. After updating, verify the new version number matches the patched release.
  7. 7. Test that the WP Job Portal functionality works correctly after the update.
  8. 8. If automatic updates are not enabled, consider enabling them for this plugin or manually checking for updates regularly.
Caveat Minor version upgrades for WordPress plugins typically have no breaking changes, but test in staging if possible

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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