CVE-2026-15600

8.6

Alior Bank · raty

The Alior Bank PrestaShop module raty is vulnerable to SQL injection in the toggleCategoryPromotionAction method, allowing authenticated backoffice users to modify database contents.

Executive summary

A high severity SQL injection vulnerability in the Alior Bank raty PrestaShop module allows an authenticated attacker to compromise database integrity.

Vulnerability

The module fails to sanitize the status POST parameter within the toggleCategoryPromotionAction method, leading to SQL injection. Successful exploitation requires an attacker to hold administrative or backoffice privileges to access category management functions.

Business impact

This vulnerability poses a significant risk to data confidentiality and integrity. An attacker with backoffice access can manipulate SQL queries to view sensitive information or modify records within the PrestaShop database. With a CVSS score of 8.6, this flaw is categorized as high severity and could lead to unauthorized administrative control over the store data if left unpatched.

Remediation

Immediate Action: Update the Alior Bank raty module to version 8.1.12 or 9.0.8 immediately to apply the necessary input sanitization patches.

Proactive Monitoring: Review database access logs and query history for unusual UPDATE commands or unexpected syntax patterns originating from the backoffice interface.

Compensating Controls: Ensure that administrative access to the PrestaShop backoffice is strictly limited to authorized personnel and protected by multi-factor authentication to reduce the likelihood of malicious exploitation.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the high severity of this SQL injection flaw, administrators must prioritize updating the raty module to the latest version. Failure to patch allows authenticated users to potentially compromise the entire store database, leading to severe operational and security consequences. Apply the recommended versions immediately to mitigate this risk.

More Alior Bank CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by K. Winiarski <kwiniarski93@proton.me>, per the CVE Program record.