dbcve.org
Js Job ManagerWordPress extension · Joomsky

CVE-2025-31867

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to after 2.0.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Authorization Bypass Through User-Controlled Key vulnerability in JoomSky JS Job Manager js-jobs allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Job Manager: from n/a through <= 2.0.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 · moderate confidence

This is an authorization bypass vulnerability in JoomSky's JS Job Manager Joomla component where a user-controlled key allows attackers to bypass access control checks. The vulnerability stems from incorrectly configured security levels that fail to properly validate user permissions before granting access to sensitive job management functions.

MitigationUpgrade JS Job Manager to version 2.0.3 or later. If no patch is available, audit all access control checks in the component and implement proper authorization validation for any user-influenced parameters.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 JS Job Manager is installed
    Log into the Joomla Administrator panel, navigate to Extensions > Manage > Manage, and search for 'JS Job Manager' or 'com_jsjobs' to confirm the component is present in the extensions list.
    Affected if The component is not listed in Joomla's extension manager, then the vulnerability does not apply.
  2. Determine installed version
    In the Joomla Extensions > Manage > Manage view, locate the JS Job Manager entry and note the version number displayed in the column. Alternatively, inspect the component's manifest XML file typically located at /administrator/components/com_jsjobs/jsjobs.xml or the main component PHP file for version constants.
    Affected if The displayed version is 2.0.2 or lower.
  3. Check if component is enabled
    In Joomla Administrator, go to Extensions > Manage > Manage, find JS Job Manager, and verify the Status column shows 'Enabled' or a green checkmark.
    Affected if The component status is enabled and version is 2.0.2 or lower.
  4. Inspect access control configuration
    Navigate to Components > JS Job Manager in the Administrator panel, then look for User Access Levels, Access Control, or Permissions settings. Check if any user groups have elevated permissions to job management functions.
    Affected if Custom access control rules or user-defined permission levels are configured for the component.
  5. Audit user-influenced parameters
    Review the JS Job Manager configuration files and any frontend/backend PHP files for parameters that accept user input (such as keys, IDs, or tokens) that could influence authorization decisions. Look for URL parameters or form inputs that modify access control behavior.
    Affected if User-controllable parameters exist in the component's code or configuration that affect permission checks.

The environment is affected if JS Job Manager is installed, enabled, and running version 2.0.2 or lower, with any custom access control configurations or user-influenced parameters present.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.2
Interim mitigation

Upgrade JS Job Manager to version 2.0.3 or later. If no patch is available, audit all access control checks in the component and implement proper authorization validation for any user-influenced parameters.

Fix this in Js Job Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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