Jms SliderPrestaShop extension · Joommasters
CVE-2023-29631
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 · uneditedPrestaShop jmsslider 1.6.0 is vulnerable to Incorrect Access Control via ajax_jmsslider.php.
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 confidenceThe jmsslider module version 1.6.0 for PrestaShop contains an Incorrect Access Control vulnerability in the ajax_jmsslider.php file. This allows unauthenticated attackers to potentially access sensitive functionality or execute unauthorized actions due to missing or insufficient access control checks in the AJAX endpoint.
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
Jms SliderPrestaShop extension
= 1.6.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check if PrestaShop is installedLook for PrestaShop installation directories or check for typical PrestaShop file structures (config/settings.inc.php, classes/Category.php, etc.)Affected if PrestaShop is present in the environment
-
Identify if the jmsslider module is presentSearch for the jmsslider module directory in the PrestaShop modules folder (commonly /modules/jmsslider/)Affected if The jmsslider module directory exists
-
Verify the jmsslider module version is 1.6.0Check the module's main PHP file (typically config.xml or the main module PHP file) for the version number, or look in the PrestaShop database in the ps_module table for the version fieldAffected if The installed version is exactly 1.6.0
-
Confirm ajax_jmsslider.php existsLook for the file ajax_jmsslider.php within the jmsslider module directoryAffected if The ajax_jmsslider.php file is present in the module
-
Verify the AJAX endpoint is accessible without authenticationAttempt to access the ajax_jmsslider.php file via HTTP request (e.g., curl or browser) without providing any authentication credentials to see if it respondsAffected if The endpoint responds without requiring authentication
The environment is affected if PrestaShop is running with the jmsslider module version 1.6.0 and the ajax_jmsslider.php file is accessible without authentication.
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 dataRestrict access to ajax_jmsslider.php by implementing proper authentication and authorization checks, or remove the file if unused. If a patched version of the jmsslider module is available, upgrade to the latest version.
Fix this in Jms Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29631 — 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-2023-29631 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