CVE-2026-30463
Received Received - Intake
SQL Injection in FuelCMS 1.5.2 Login.php Allows Data Exposure

Publication date: 2026-03-26

Last updated on: 2026-03-30

Assigner: MITRE

Description
Daylight Studio FuelCMS v1.5.2 was discovered to contain a SQL injection vulnerability via the /controllers/Login.php component.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-26
Last Modified
2026-03-30
Generated
2026-05-07
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
thedaylightstudio fuel_cms 1.5.2
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 Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

CVE-2026-30463 is a critical SQL Injection vulnerability that allows attackers to extract all information from the database and reset passwords of arbitrary users, including administrators.

This high impact on confidentiality and integrity can lead to unauthorized access to sensitive personal data, which may violate data protection regulations such as GDPR and HIPAA.

Specifically, the ability to extract sensitive data and modify user credentials undermines the security controls required to protect personal and health information, potentially resulting in non-compliance with these standards.


Can you explain this vulnerability to me?

CVE-2026-30463 is a high-severity SQL Injection vulnerability found in FuelCMS version 1.5.2, specifically in the password reset functionality at the endpoint /fuel/login/reset/.

The vulnerability arises from unsafe and unsanitized handling of the email and _token parameters, allowing attackers to inject specially crafted SQL queries.

Attackers can exploit this vulnerability by sending crafted POST requests that manipulate these parameters to execute arbitrary SQL commands on the backend database.

This enables attackers to extract sensitive information, reset passwords of arbitrary users including administrators, and modify or delete website elements.


How can this vulnerability impact me? :

This vulnerability can have severe impacts on confidentiality, integrity, and availability of the affected system.

  • Confidentiality: Attackers can extract all information from the database, exposing sensitive data.
  • Integrity: Attackers can forcibly reset any user's password, including admin accounts, and modify or delete website elements.
  • Availability: While attackers cannot fully shut down the application, they can prevent legitimate users from logging in by altering or deleting their credentials.

Exploitation requires the attacker to have a valid password reset token, which can be obtained by accessing the victim's email or exploiting other vulnerabilities.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring and testing the password reset endpoint `/fuel/login/reset/` for SQL injection attempts in the `email` and `_token` POST parameters.

Detection involves sending crafted POST requests with SQL injection payloads to observe different server responses such as HTTP 302 redirects or HTTP 500 errors, which indicate possible injection points.

Example commands to test this vulnerability could include using curl to send POST requests with injection payloads, for instance:

  • curl -X POST https://targetsite/fuel/login/reset/ -d 'email=admin" OR 1=1--& _token=validtoken'
  • curl -X POST https://targetsite/fuel/login/reset/ -d 'email=*/ or " - - -& _token=qqq'

Analyzing server responses for error messages or unexpected behavior can help confirm the presence of the SQL injection vulnerability.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the password reset endpoint to trusted users or IP addresses to reduce exposure.

Implementing web application firewall (WAF) rules to detect and block SQL injection payloads targeting the `email` and `_token` parameters can help prevent exploitation.

Since no official patch exists and the vendor is unlikely to update the software, consider disabling the password reset functionality temporarily if possible.

Monitor logs for suspicious password reset attempts and unusual activity related to user account changes.

Plan to upgrade or migrate to a more secure CMS solution that is actively maintained and patched.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart