dbcve.org
JobwpWordPress extension · Hmplugin

CVE-2023-48288

HIGH · 7.5 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 2.2 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
Exposure of Sensitive Information to an Unauthorized Actor 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.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 · moderate confidence

An information disclosure vulnerability in the WordPress JobWP plugin (versions through 2.1) allows unauthenticated attackers to access sensitive data. The specific attack vector and exact nature of exposed information are not detailed in the CVE reference.

MitigationUpdate JobWP plugin to the latest version if a security patch is available; otherwise, restrict access to plugin-related endpoints and review server configuration for exposure vectors.

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.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
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 is installed
    Check for the plugin directory at /wp-content/plugins/jobwp/ or search for 'jobwp' in /wp-content/plugins/ folder
    Affected if The plugin directory exists and contains JobWP files
  2. Identify installed plugin version
    Open the main plugin file (usually jobwp.php) and locate the version in the plugin header comment (look for 'Version: x.x')
    Affected if Version field shows a number less than 2.2
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if JobWP shows as 'Active', or check the wp_options table for active_plugins option
    Affected if Plugin status is Active and accessible to unauthenticated users
  4. Check for unauthenticated access to plugin endpoints
    Test accessing common plugin URLs without login (e.g., any jobwp-related AJAX endpoints or frontend submission forms)
    Affected if Requests return data without requiring authentication

If the JobWP plugin is installed with a version lower than 2.2 and is active, the environment is vulnerable to CVE-2023-48288 and exposed to unauthenticated information disclosure.

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 or later
Fixed in 2.2
Interim mitigation

Update JobWP plugin to the latest version if a security patch is available; otherwise, restrict access to plugin-related endpoints and review server configuration for exposure vectors.

Recommended fix High confidence

JobWP version 2.2

  1. 1. Backup the WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'JobWP' (Job Board and Recruitment Plugin).
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.2 or later.
  6. 6. If no update appears, manually download the latest version from the WordPress plugin repository or the vendor's website.
  7. 7. Deactivate the existing plugin, then delete it, and upload/install the new version 2.2 or later.
  8. 8. Reactivate the plugin after installation.

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

Fix this in Jobwp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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