Js Job ManagerWordPress extension · Joomsky
CVE-2025-32627
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 · uneditedImproper 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 · high confidenceThe JoomSky JS Job Manager Joomla extension (js-jobs) versions up to 2.0.2 contains an improper control of filename vulnerability in PHP include/require statements, allowing authenticated attackers to perform PHP Local File Inclusion (LFI) attacks by manipulating file path 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
<= 2.0.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify JS Job Manager installationCheck your Joomla administrator panel under Components menu for JS Job Manager, or inspect the file /components/com_jsjobs/jsjobs.xml for the <version> tagAffected if The extension is present and version is 2.0.2 or lower
-
Locate the vulnerable component fileInspect the component directory /components/com_jsjobs/ for PHP files that contain include, include_once, require, or require_once statements with variable file pathsAffected if Files using dynamic file inclusion without proper sanitization are found
-
Verify authentication requirement for the componentCheck if the component requires user authentication by reviewing the component's entry point file and any access controls defined in the Joomla manifestAffected if The component accepts authenticated user requests with manipulable file path parameters
-
Confirm the file inclusion vulnerability existsReview identified PHP include/require code paths to verify they accept user-supplied input without validation (such as $_GET or $_POST parameters used in file paths)Affected if Unvalidated user input is directly used in include/require statements
Your environment is affected if JS Job Manager version 2.0.2 or lower is installed and the component exposes file inclusion functionality to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade JS Job Manager to the latest version that addresses this vulnerability; if no patch is available, implement input validation and use whitelisting for file inclusion paths at the web server or application layer.
Fix this in Js Job Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32627 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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