CVE-2023-27034: PrestaShop jmsblog module SQL injection

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 19 September 2026. Confidence: medium.

critical priorityCVSS 9.8 with network reachability, no authentication, no user interaction, and high EPSS percentile make this a high-urgency issue despite the absence of KEV listing.

What it is

The jmsblog module version 2.5.5 for PrestaShop contains a SQL injection vulnerability (CWE-89). The flaw is remotely reachable without authentication or user interaction, and the CVSS 3.1 base score is 9.8 (critical).

Impact

An unauthenticated attacker can inject arbitrary SQL into the module's queries, potentially reading, modifying, or deleting database contents. The CVSS vector indicates high impact to confidentiality, integrity, and availability.

Attack surface

The CVSS vector is AV:N/AC:L/PR:N/UI:N, meaning the attack is network-reachable, low complexity, requires no privileges, and needs no user interaction. The description does not specify the exact parameter or endpoint, so the precise injection point is not documented in this record.

Exploitation

The CVE is not listed in CISA KEV, but EPSS is 0.58743 (99.062 percentile), indicating a high modeled probability of exploitation activity. The only references are patch and third-party advisory links; no public exploit code or in-the-wild reporting is cited in this record.

What to do

• Apply the vendor patch referenced in the friends-of-presta security advisory for jmsblog.
• If patching is not immediately possible, disable or remove the jmsblog module until it can be updated.
• Restrict network access to the PrestaShop front office and admin paths where the module is exposed.
• Review database logs and application logs for anomalous SQL patterns targeting the module.
• Confirm the deployed jmsblog version and replace any instance still at 2.5.5.

Detection

• Monitor web server and WAF logs for SQL metacharacters (quotes, UNION, OR 1=1, comment sequences) in requests to jmsblog endpoints.
• Alert on database errors or unusual query volume originating from the PrestaShop application user.
• Baseline normal jmsblog request parameters and flag deviations, especially unauthenticated requests to module routes.
• Correlate outbound database activity with front-end request logs to spot injection-driven data access.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.