dbcve.org
Js Job ManagerWordPress extension · Joomsky

CVE-2025-32146

HIGH · 8.8 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to after 2.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in JoomSky JS Job Manager js-jobs allows PHP Local File Inclusion.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

Improper control of filename parameters in PHP include/require statements within JoomSky JS Job Manager (js-jobs) for Joomla allows authenticated or unauthenticated attackers to include local PHP files, potentially leading to code execution. This is a classic Local File Inclusion (LFI) vulnerability in the component up to version 2.0.2.

MitigationUpdate to the latest patched version of JS Job Manager immediately. If no patch is available, disable the js-jobs component or implement strict input validation and directory access controls on the web server to prevent traversal outside intended directories.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm JS Job Manager component is installed
    Log into the Joomla administrator panel and navigate to Extensions > Manage > Manage. Search for 'js-jobs' or 'JS Job Manager' in the installed extensions list. Alternatively, check the /administrator/components/ directory for a js-jobs folder.
    Affected if The js-jobs component is found to be installed on the Joomla site
  2. Verify the installed version number
    In the Joomla administrator panel, go to Components > JS Job Manager (or check the manifest XML file in /administrator/components/com_js_jobs/ for the <version> tag). Compare the version against the affected range.
    Affected if The installed version is 2.0.2 or lower
  3. Check if the component is enabled
    In Joomla administrator, go to Extensions > Modules or Components and verify the JS Job Manager component status. Also check if any public-facing menu items link to js-jobs functionality.
    Affected if The component is enabled and accessible via the website frontend or backend
  4. Review web server access logs for LFI patterns
    Search access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to the js-jobs component containing path traversal sequences such as '../', '..\', or absolute file paths in query parameters.
    Affected if Log entries show suspicious requests with file path parameters targeting the js-jobs component
  5. Inspect component source for include/require usage
    Examine PHP files in /components/com_js_jobs/ and /administrator/components/com_js_jobs/ for include(), require(), include_once(), or require_once() statements that use unfiltered user input from $_GET, $_POST, or $_REQUEST superglobals.
    Affected if The component code uses include/require with unsanitized input from request parameters

A Joomla site is affected if the JS Job Manager component is installed, enabled, and running version 2.0.2 or lower, allowing unauthenticated or authenticated users to manipulate file inclusion parameters.

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

Update to the latest patched version of JS Job Manager immediately. If no patch is available, disable the js-jobs component or implement strict input validation and directory access controls on the web server to prevent traversal outside intended directories.

Fix this in Js Job Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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