Jupiter X CoreWordPress extension · Artbees
CVE-2022-1656
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 · uneditedVulnerable versions of the JupiterX Theme (<=2.0.6) allow any logged-in user, including subscriber-level users, to access any of the functions registered in lib/api/api/ajax.php, which also grant access to the jupiterx_api_ajax_ actions registered by the JupiterX Core Plugin (<=2.0.6). This includes the ability to deactivate arbitrary plugins as well as update the theme’s API key.
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 JupiterX Theme (≤2.0.6) and Core Plugin (≤2.0.6) expose AJAX functions in lib/api/api/ajax.php without proper authorization checks. Any authenticated user, including subscriber-level accounts, can invoke these endpoints to perform privileged actions such as deactivating arbitrary plugins and modifying theme API settings.
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
Jupiter X CoreWordPress extension
<= 2.0.6
JupiterxWordPress extension
<= 2.0.6CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check JupiterX Theme versionLocate the style.css file in wp-content/themes/jupiterx/ and read the Version header, or query the WordPress themes API endpoint /wp-admin/admin-ajax.php?action=jupiterx_versionAffected if The installed version is 2.0.6 or lower
-
Check JupiterX Core Plugin versionNavigate to Plugins in WordPress admin and find 'Jupiter X Core' in the list, or inspect the plugin header in wp-content/plugins/jupiterx-core/jupiterx-core.php for the Version fieldAffected if The installed version is 2.0.6 or lower
-
Verify vulnerable AJAX file existsCheck for the existence of lib/api/api/ajax.php within either the theme directory (wp-content/themes/jupiterx/lib/api/api/ajax.php) or the core plugin directory (wp-content/plugins/jupiterx-core/lib/api/api/ajax.php)Affected if The file exists in either location
-
Test AJAX authorization vulnerabilitySend an authenticated AJAX request as a subscriber-level user to endpoints such as jupiterx_core_plugin_deactivate or jupiterx_api_settings_update in wp-admin/admin-ajax.php, observing whether the request succeeds without proper capability verificationAffected if The request executes successfully without returning a capability or authorization error
-
Check WordPress user registration settingsNavigate to Settings > General in WordPress admin and verify the 'Membership' setting - whether 'Anyone can register' is enabled and what default role is assignedAffected if Anyone can register is enabled, allowing untrusted subscriber-level accounts to access the vulnerable AJAX endpoints
Your environment is affected if JupiterX Theme or Core Plugin is at version 2.0.6 or lower AND the vulnerable ajax.php file exists AND your site allows untrusted user registration that could exploit the missing authorization checks.
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 to JupiterX Theme and Core Plugin version 2.0.7 or later which implements proper capability checks. Until patched, disable the vulnerable AJAX endpoints or restrict site registration to trusted users only.
Fix this in Jupiter X Core
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1656 — 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-2022-1656 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