dbcve.org
JobwpWordPress extension · Hmplugin

CVE-2023-29384

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to after 2.0 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
Unrestricted Upload of File with Dangerous Type vulnerability in HM Plugin WordPress Job Board and Recruitment Plugin – JobWP.This issue affects WordPress Job Board and Recruitment Plugin – JobWP: from n/a through 2.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 confidence

Unrestricted file upload vulnerability in the JobWP WordPress plugin allows attackers to upload dangerous file types (likely executable scripts) without proper validation, potentially enabling remote code execution on the affected WordPress site.

MitigationUpdate JobWP plugin to the latest version immediately; if no patch exists, disable the plugin and implement web application firewall rules to block malicious file uploads.

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
JobwpWordPress extension
Affected:<= 2.0

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. Confirm JobWP plugin installation and version
    Access WordPress admin dashboard > Plugins > Installed Plugins > Look for 'JobWP' or 'Jobwp' by Hmplugin. Check the version number displayed under the plugin name. Alternatively, inspect the file /wp-content/plugins/jobwp/readme.txt and look for the 'Stable tag:' entry.
    Affected if Plugin version is 2.0 or lower, or the version cannot be determined (readme.txt missing or inaccessible)
  2. Identify accessible file upload functionality
    Navigate to the WordPress admin panel and locate the JobWP plugin settings page. Look for any job posting form, resume upload feature, or file attachment input that allows visitors or users to submit files. Note the URL endpoint used for file uploads.
    Affected if Any publicly accessible file upload form or input field exists on the site (job submission, resume upload, etc.)
  3. Review uploaded files directory
    Check the wp-content/uploads/ directory (or custom upload path configured in WordPress) for recently added files. Look for file types that should not be present: .php, .phtml, .php5, .php7, .js, .exe, .sh, .bat, .zip archives containing executable content.
    Affected if Suspicious executable files (.php, .phtml, etc.) exist in upload directories, especially with randomized names or created around the time of suspected attack
  4. Check for new administrator accounts
    In WordPress admin, go to Users > All Users. Look for unfamiliar administrator accounts created recently, especially with usernames like 'admin', 'wp-admin', 'system', or foreign language characters.
    Affected if Unexpected administrator accounts exist that were not created by known site administrators
  5. Inspect .htaccess and index.php for web shell code
    Examine the wp-content/plugins/jobwp/ directory for modified .htaccess files or index.php files containing base64_decode, eval, shell_exec, system, or similar PHP functions used for remote code execution.
    Affected if Web shell code or backdoor scripts are found within the plugin directory or its uploaded files

You are affected if JobWP plugin version is 2.0 or lower AND any file upload functionality (job application, resume submission) is enabled on your site.

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 a release after 2.0
Interim mitigation

Update JobWP plugin to the latest version immediately; if no patch exists, disable the plugin and implement web application firewall rules to block malicious file uploads.

Recommended fix Moderate confidence

Latest version of JobWP (version > 2.0)

  1. Backup your WordPress site database and files before making any changes
  2. Verify your current JobWP plugin version by navigating to Plugins > Installed Plugins in WordPress admin
  3. Update JobWP plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the plugin is functioning correctly
  5. Ensure file upload functionality is working as expected for legitimate job application submissions
  6. Consider reviewing any uploaded files to ensure no malicious files were uploaded during the vulnerable period

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

Fix this in Jobwp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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