dbcve.org
Wp Job PortalWordPress extension · Wpjobportal

CVE-2025-48274

HIGH · 7.5 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 2.3.3 or later.
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in wpjobportal WP Job Portal wp-job-portal allows Blind SQL Injection.This issue affects WP Job Portal: from n/a through <= 2.3.2.

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

Blind SQL Injection vulnerability in WP Job Portal WordPress plugin (versions <= 2.3.2) allows unauthenticated attackers to inject malicious SQL commands via unsanitized user inputs in the plugin, potentially allowing data exfiltration or database manipulation.

MitigationUpdate WP Job Portal to the latest version beyond 2.3.2 when available. If no patch exists, consider disabling the plugin until a fix is released, or implement web application firewall rules to block SQL injection 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.3

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 WP Job Portal plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Job Portal' or 'Wpjobportal Wp Job Portal' in the list. Alternatively, check if the /wp-content/plugins/ directory contains a folder named 'wpjobportal'.
    Affected if The plugin folder exists in the WordPress plugins directory, indicating the plugin is installed.
  2. Check if the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify whether WP Job Portal shows as 'Active' or has an active status indicator. If using WP-CLI, run: wp plugin status wpjobportal
    Affected if The plugin is activated and accessible on the site.
  3. Identify installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on the WP Job Portal plugin to view its details, which typically display the version number. Or inspect the file: /wp-content/plugins/wpjobportal/readme.txt and look for the 'Stable tag:' or 'Version:' entry near the top. Using WP-CLI: wp plugin get wpjobportal --fields=version
    Affected if The version displayed is 2.3.2 or lower.
  4. Confirm vulnerability exposure
    Since this is a blind SQL injection via unsanitized user inputs in the plugin itself, any public-facing usage of the plugin exposes the site. Check if the plugin shortcodes or components are used on any publicly accessible pages by searching for '[wpjobportal' or related shortcodes in your posts/pages, or if the plugin's frontend functionality is accessible.
    Affected if The plugin is active and its features are accessible to unauthenticated users, which is the default configuration.

Your site is affected if the WP Job Portal plugin is installed and active with a version of 2.3.2 or lower, as this allows unauthenticated SQL injection via the plugin's user input fields.

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.3 or later
Fixed in 2.3.3
Interim mitigation

Update WP Job Portal to the latest version beyond 2.3.2 when available. If no patch exists, consider disabling the plugin until a fix is released, or implement web application firewall rules to block SQL injection attack patterns.

Recommended fix Moderate confidence

WP Job Portal version 2.3.3

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Job Portal in the list
  4. If an update is available, click 'Update Now' to upgrade to version 2.3.3
  5. Alternatively, download version 2.3.3 from the official WordPress plugin repository or WP Job Portal website
  6. Deactivate and delete the current plugin if automatic update does not work, then upload and activate version 2.3.3
  7. Verify the plugin version shows 2.3.3 after upgrade
  8. Test critical job posting and application functionality to ensure the upgrade did not break existing features

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

Fix this in Wp Job Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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