dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-14293

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-11
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
The WP Job Portal plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 2.4.0 via the 'downloadCustomUploadedFile' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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 (versions up to 2.4.0) contains an arbitrary file read vulnerability in the downloadCustomUploadedFile function. Authenticated attackers with Subscriber-level access can exploit this to read sensitive files on the server by manipulating file path parameters, potentially exposing configuration files, credentials, or other sensitive data.

MitigationUpdate the WP Job Portal plugin to a version newer than 2.4.0 as soon as a patch is available. Until then, restrict subscriber-level account creation and monitor for suspicious file access patterns.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if WP Job Portal plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Job Portal' or check the plugin directory /wp-content/plugins/ for the wp-job-portal folder
    Affected if The plugin is present in the plugins directory
  2. Determine installed WP Job Portal version
    In WordPress admin, go to Plugins > Installed Plugins and look at the version number listed under WP Job Portal, or check the main plugin file header in wp-content/plugins/wp-job-portal/wp-job-portal.php
    Affected if The version is 2.4.0 or lower (any version up to and including 2.4.0)
  3. Identify subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the role column for any accounts with 'Subscriber' role, or query the wp_usermeta table for user_role_meta containing 'subscriber'
    Affected if Any subscriber-level accounts exist in the WordPress installation
  4. Monitor for access to the vulnerable downloadCustomUploadedFile function
    Review web server access logs (Apache error.log, Nginx access.log) or WordPress audit logs for requests to the downloadCustomUploadedFile function, typically found in admin controller files under wp-job-portal/controllers/
    Affected if There are requests to the downloadCustomUploadedFile function from authenticated users, especially subscribers
  5. Inspect file permissions on sensitive system files
    Check file permissions on wp-config.php, .htaccess, and other sensitive configuration files in the web root - ensure they are not world-readable (recommended: 644 for files, 755 for directories)
    Affected if Sensitive configuration files have overly permissive access (world-readable or group-readable)

A user is affected if the WP Job Portal plugin version is 2.4.0 or lower AND subscriber-level accounts exist in WordPress, allowing authenticated attackers to exploit the arbitrary file read vulnerability.

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 a version newer than 2.4.0 as soon as a patch is available. Until then, restrict subscriber-level account creation and monitor for suspicious file access patterns.

Recommended fix Moderate confidence

Latest version greater than 2.4.0 (verify exact version at plugins.trac.wordpress.org or vendor site)

  1. Check the current version of the WP Job Portal plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP Job Portal and note the current version number
  4. Visit the WordPress Plugin Directory or the official vendor site to identify the latest version that addresses this vulnerability
  5. Update the plugin to the latest available version that includes the security fix for CVE-2025-14293
  6. After updating, verify the fix by testing that the 'downloadCustomUploadedFile' function no longer allows path traversal
  7. Ensure any users with Subscriber-level access have legitimate need for such permissions
Caveat Review plugin changelog for any breaking changes between current version and the fixed version before upgrading in production environments

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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