CVE-2026-53690
Received Received - Intake

SQL Injection in Redeight CMS

Vulnerability report for CVE-2026-53690, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: CERT.PL

Description

An SQL Injection vulnerability exists in Redeight CMS version 1.0 via the "userEmail" parameter in the POST "/admin/index.php" login endpoint. The application fails to sanitize user input and directly interpolates it into SQL queries without using prepared statements, which allows unauthenticated remote attackers to execute arbitrary SQL commands and extract sensitive database information.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-06-30
Generated
2026-06-30
AI Q&A
2026-06-30
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
redeight cms 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Mitigation Strategies

Immediate mitigation steps include restricting access to the /admin/index.php login endpoint to trusted IP addresses or networks to reduce exposure.

Implement web application firewall (WAF) rules to block SQL injection attempts targeting the userEmail parameter.

If possible, update or patch Redeight CMS to a version that fixes this vulnerability.

As a temporary workaround, sanitize and validate all inputs on the server side, especially the userEmail parameter, to prevent SQL injection.

Compliance Impact

The SQL Injection vulnerability in Redeight CMS version 1.0 allows unauthenticated remote attackers to execute arbitrary SQL commands and extract sensitive database information. This exposure of sensitive data can lead to non-compliance with common standards and regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access and breaches.

Failure to properly sanitize user input and prevent data breaches through vulnerabilities like SQL Injection can result in violations of data protection requirements, potentially leading to legal and financial consequences under these regulations.

Executive Summary

CVE-2026-53690 is an SQL Injection vulnerability found in Redeight CMS version 1.0. It occurs via the "userEmail" parameter in the POST "/admin/index.php" login endpoint. The application does not properly sanitize user input and directly inserts it into SQL queries without using prepared statements. This flaw allows unauthenticated remote attackers to execute arbitrary SQL commands and extract sensitive information from the database.

Impact Analysis

This vulnerability can have severe impacts as it allows attackers to execute arbitrary SQL commands remotely without authentication. This can lead to unauthorized access to sensitive database information, data theft, data manipulation, or even complete compromise of the affected system.

Detection Guidance

This vulnerability is an SQL Injection in the userEmail parameter of the POST /admin/index.php login endpoint in Redeight CMS version 1.0. Detection can involve monitoring for unusual or malicious SQL payloads sent to this endpoint.

You can detect attempts by capturing and analyzing HTTP POST requests to /admin/index.php and inspecting the userEmail parameter for suspicious SQL syntax such as ' OR '1'='1, UNION SELECT, or other SQL keywords.

Example commands to detect such activity might include using network traffic analysis tools like tcpdump or Wireshark to capture traffic, or using web server logs to search for suspicious patterns.

  • Using grep on web server logs to find suspicious userEmail inputs: grep -i "userEmail=.*(\'|\"|;|--|union|select)" /var/log/apache2/access.log
  • Using tcpdump to capture HTTP POST requests to /admin/index.php: tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep "/admin/index.php"

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53690. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart