dbcve.org
Js Job ManagerWordPress extension · Joomsky

CVE-2023-31087

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in JoomSky JS Job Manager plugin <= 2.0.0 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in JoomSky JS Job Manager WordPress plugin versions 2.0.0 and earlier. The lack of proper anti-CSRF tokens on state-changing operations allows attackers to trick authenticated administrators into unknowingly executing unwanted actions such as modifying job listings or user data.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and state-changing requests within the plugin, and validate these tokens server-side before processing any changes. Update to the latest patched version if available.

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
Js Job ManagerWordPress extension
Affected:< 2.0.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check the installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate 'JoomSky JS Job Manager', and read the version number from the plugin description. Alternatively, open the main plugin file (typically js-job-manager.php) and locate the 'Version' header in the plugin comment block.
    Affected if The installed version is 2.0.0 or earlier (any version below 2.0.1)
  2. Locate the main plugin PHP file
    Access the WordPress wp-content/plugins/js-job-manager/ directory via file manager or FTP, and identify the primary PHP file (commonly js-job-manager.php or similar).
    Affected if The plugin file exists and the version check above shows an affected version
  3. Inspect state-changing functions for nonce verification
    Open the main plugin PHP file and search for functions that handle form submissions, data modifications, or administrative actions (keywords: add_action, do_action, $_POST, $_GET). Examine whether each state-changing function includes nonce verification (keywords: check_admin_referer, wp_verify_nonce, verify_nonce).
    Affected if State-changing operations lack nonce validation code (check_admin_referer, wp_verify_nonce, or nonce_field calls are missing)
  4. Check AJAX handlers for CSRF protection
    Search the plugin files for AJAX action hooks (wp_ajax_ and wp_ajax_nopriv_). For each handler, verify that the callback function includes nonce verification before processing the request.
    Affected if AJAX handlers process requests without verifying a nonce token first

You are affected if the installed plugin version is below 2.0.1 and any state-changing operations (form submissions, admin actions, or AJAX requests) lack proper nonce verification code.

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.0.1 or later
Fixed in 2.0.1
Interim mitigation

Implement anti-CSRF tokens (nonces) on all form submissions and state-changing requests within the plugin, and validate these tokens server-side before processing any changes. Update to the latest patched version if available.

Recommended fix Moderate confidence

2.0.1 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find JS Job Manager by JoomSky
  5. Click 'Update now' if an update is available, or manually update to version 2.0.1 or later
  6. Verify the plugin version shows 2.0.1 or higher after updating
  7. Test critical job posting and application submission functionality to confirm the update didn't break legitimate features

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

Fix this in Js Job Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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