dbcve.org
Wp Job PortalWordPress extension · Wpjobportal

CVE-2025-47438

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in wpjobportal WP Job Portal wp-job-portal allows PHP Local File Inclusion.This issue affects WP Job Portal: from n/a through <= 2.3.1.

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 through 2.3.1 contains a PHP Local File Inclusion vulnerability due to improper control of filenames in include/require statements. This allows unauthenticated attackers to include arbitrary local PHP files, potentially leading to remote code execution.

MitigationImmediately disable or remove the WP Job Portal plugin until an official security patch is available. As a temporary measure, deploy WAF rules to block directory traversal and file inclusion attack patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Job PortalWordPress extension
Affected:< 2.3.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate WP Job Portal plugin installation
    Check the WordPress plugins directory for the wp-job-portal folder. Common paths: wp-content/plugins/wp-job-portal/ or /var/www/html/wp-content/plugins/wp-job-portal/
    Affected if The plugin folder does not exist - the plugin is not installed and is not affected
  2. Identify installed plugin version
    Open the main plugin PHP file (e.g., wp-job-portal.php) and locate the version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry
    Affected if Version is 2.3.1 or below - the vulnerability is present in these versions
  3. Verify plugin is active
    Query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'; Or use wp-cli: wp plugin list --status=active --name=wp-job-portal
    Affected if The plugin appears in active plugins - the vulnerable code can be reached via HTTP requests
  4. Confirm vulnerable file inclusion code exists
    Search plugin source files for dynamic include/require statements using variable input: grep -r 'include.*\$_' or grep -r 'require.*\$_' within the wp-job-portal/ directory
    Affected if Dynamic file inclusion using $_GET, $_POST, or $_REQUEST parameters is found - the LFI vulnerability is present and exploitable

If WP Job Portal plugin versions 2.3.1 or below are installed and active, the environment is vulnerable to CVE-2025-47438 and should be considered affected.

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
Upgrade available Upgrade to 2.3.2 or later
Fixed in 2.3.2
Interim mitigation

Immediately disable or remove the WP Job Portal plugin until an official security patch is available. As a temporary measure, deploy WAF rules to block directory traversal and file inclusion attack patterns.

Recommended fix High confidence

WP Job Portal version 2.3.2

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP Job Portal in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.3.2 of the plugin
  5. Verify the plugin version shows 2.3.2 after updating
  6. Test that the affected functionality works correctly

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

Fix this in Wp Job Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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