dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2010

HIGH · 7.5 CVSS v3.1 Published 2025-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin plugin for WordPress is vulnerable to SQL Injection via the 'jobwp_upload_resume' parameter in all versions up to, and including, 2.3.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 JobWP WordPress plugin fails to properly escape the 'jobwp_upload_resume' parameter and does not use prepared statements for the SQL query, allowing unauthenticated attackers to inject arbitrary SQL code and extract sensitive database information.

MitigationUpdate the JobWP plugin to a version beyond 2.3.9, which should contain the fix for proper input sanitization and prepared SQL statements.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify JobWP plugin installation
    Check if the JobWP plugin is active on the WordPress site. In WordPress admin, go to Plugins > Installed Plugins and look for 'JobWP' or use wp-cli: wp plugin list --status=active --name=jobwp
    Affected if JobWP plugin is not installed or not active
  2. Determine installed JobWP version
    In WordPress admin, click on the JobWP plugin to view its details and note the version number. Alternatively, check the main plugin file (typically wp-content/plugins/jobwp/jobwp.php) for the 'Version' header comment, or run: grep -i 'Version:' wp-content/plugins/jobwp/jobwp.php
    Affected if Version is 2.3.9 or lower (the fixed version is beyond 2.3.9)
  3. Confirm the vulnerable parameter is reachable
    Identify if the jobwp_upload_resume functionality is exposed on the site. This is typically a job application form with resume upload capability. Check for pages or shortcodes containing job application forms (often via [jobwp] shortcode or similar). The vulnerability lies in the resume upload parameter processing.
    Affected if Job application forms accepting resume uploads are publicly accessible without authentication
  4. Inspect code for prepared statements
    Examine the plugin's PHP files that handle the jobwp_upload_resume parameter (typically in the main plugin file or resume handling module). Look for SQL queries using $wpdb->prepare() or similar prepared statement functions. Search for patterns like 'jobwp_upload_resume' in the code.
    Affected if SQL queries handling jobwp_upload_resume do NOT use $wpdb->prepare() or parameterized queries, using direct variable insertion instead

The environment is affected if JobWP plugin version 2.3.9 or lower is active AND the job application resume upload feature is accessible, AND the code lacks prepared statements for the jobwp_upload_resume parameter in SQL queries.

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 JobWP plugin to a version beyond 2.3.9, which should contain the fix for proper input sanitization and prepared SQL statements.

Recommended fix High confidence

Upgrade to the latest version of JobWP (any version above 2.3.9)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin
  4. Click 'Update now' if an update is available, or manually update to the latest version
  5. Verify the update completed successfully
  6. Consider backing up the site before performing updates

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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