dbcve.org
Wp Job PortalWordPress extension · Wpjobportal

CVE-2024-52389

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 2.2.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpjobportal WP Job Portal wp-job-portal allows Stored XSS.This issue affects WP Job Portal: from n/a through <= 2.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

A stored cross-site scripting (XSS) vulnerability exists in the WP Job Portal WordPress plugin (versions up to 2.2.0) where user-supplied input is not properly sanitized before being stored and rendered in web pages, allowing attackers to inject malicious JavaScript that executes in the browsers of other users viewing the affected content.

MitigationUpdate WP Job Portal to the latest version which includes proper input sanitization and output encoding. Until an official patch is available, implement Web Application Firewall rules to filter XSS payloads and review all user input fields in the plugin for proper sanitization.

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.2.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP Job Portal' or 'Wpjobportal Wp Job Portal' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is active.
  2. Determine the installed plugin version
    In the Plugins list, click on 'WP Job Portal' to view plugin details, or check the plugin header comment in /wp-content/plugins/wpjobportal/ directory. The version number is displayed in the plugin metadata.
    Affected if The installed version is 2.2.0 or lower (any version < 2.2.1).
  3. Identify accessible user input fields
    Visit the frontend job portal pages where users can submit job applications, resumes, or contact forms. Common entry points include job listing pages, application forms, and user profile submission pages.
    Affected if User input forms are publicly accessible without admin privileges.
  4. Check database for stored XSS payloads
    Query the WordPress database tables where plugin data is stored (typically tables prefixed with wp_wpjobportal_). Look for script tags, javascript:, or other XSS patterns in fields like job applications, resumes, or message content.
    Affected if Malicious script tags or encoded JavaScript payloads are found stored in the plugin database tables.
  5. Review browser console for XSS execution
    Use browser developer tools (F12) to inspect the Console tab while viewing job portal pages. Check the Network tab for any unexpected external requests to attacker-controlled domains.
    Affected if JavaScript errors appear related to injected scripts, or unexpected network requests to unknown domains are observed.

A user is affected if the WP Job Portal plugin version is below 2.2.1 and user-submitted content (job applications, resumes, or form inputs) can be viewed by other users without proper sanitization.

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.2.1 or later
Fixed in 2.2.1
Interim mitigation

Update WP Job Portal to the latest version which includes proper input sanitization and output encoding. Until an official patch is available, implement Web Application Firewall rules to filter XSS payloads and review all user input fields in the plugin for proper sanitization.

Recommended fix Moderate confidence

2.2.1

  1. Back up your WordPress site database and files before performing any updates
  2. Navigate to WordPress admin dashboard > Plugins > WP Job Portal
  3. If automatic updates are enabled, the plugin should update automatically; otherwise, click 'Update Now' to update WP Job Portal to version 2.2.1 or later
  4. Verify the plugin version shows 2.2.1 or higher after updating
  5. Clear any caching plugins or server-side caches if applicable
  6. Test the affected functionality to confirm the XSS vulnerability is remediated
Caveat Point release upgrade - minimal risk of breaking changes, but test in staging first if available

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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