dbcve.org
Js Job ManagerWordPress extension · Joomsky

CVE-2023-28689

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
71/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
Missing Authorization vulnerability in JoomSky JS Job Manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Job Manager: from n/a through 2.0.0.

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

Missing authorization vulnerability in JoomSky JS Job Manager allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or manipulate job postings and related functionality they should not have permission to access.

MitigationUpdate JS Job Manager to the latest version (beyond 2.0.0) to obtain the vendor patch. If immediate update is not possible, restrict network access to the administrative interface to trusted IPs only as a temporary workaround.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Confirm JS Job Manager is installed
    Locate the JS Job Manager component in your Joomla installation by checking the /administrator/components/com_jsjobs/ directory or querying the #__extensions table for 'com_jsjobs'
    Affected if The component directory or database entry exists and the extension is enabled
  2. Identify the installed version
    Check the manifest file (typically manifest.xml) in the component directory, or query the #__extensions table for the 'version' field where element='com_jsjobs'
    Affected if The version number returned is less than 2.0.1 (for example, 2.0.0, 1.x.x, or unversioned)
  3. Verify access control configuration is in place
    Access the component's access control settings in the Joomla administrator panel under Components > JS Job Manager > Configuration > Access Control Settings, and verify that security level permissions are explicitly defined for each user group
    Affected if Security levels are not explicitly configured, set to 'None', or allow unauthorized guest/public access to administrative functions

You are affected if JS Job Manager is installed with a version prior to 2.0.1 and the access control security levels are either misconfigured or allow unauthorized access to protected job posting functions.

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

Update JS Job Manager to the latest version (beyond 2.0.0) to obtain the vendor patch. If immediate update is not possible, restrict network access to the administrative interface to trusted IPs only as a temporary workaround.

Recommended fix High confidence

2.0.1

  1. 1. Create a full backup of the Joomla site and database before making any changes
  2. 2. Download JS Job Manager version 2.0.1 or later from the official vendor source
  3. 3. Navigate to Joomla Administrator > Extensions > Manage > Install
  4. 4. Upload and install the updated JS Job Manager package
  5. 5. Clear any Joomla and browser caches after the update
  6. 6. Verify the extension is running version 2.0.1 or higher in Extensions > Manage > Manage

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
  • 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-2023-28689 — 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-28689 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