CVE-2026-14639
Received Received - Intake

SQL Injection in CodeAstro Ecommerce Website

Publication date: 2026-07-04

Last updated on: 2026-07-04

Assigner: VulDB

Description
A vulnerability has been found in CodeAstro Ecommerce Website 1.0. This impacts an unknown function of the file /ecommerce-website-php/customer/my_account.php?edit_account. Such manipulation of the argument c_name leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-04
Last Modified
2026-07-04
Generated
2026-07-04
AI Q&A
2026-07-04
EPSS Evaluated
N/A
NVD
CVE-2026-14639
EUVD
EUVD-2026-41683

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
codeastro ecommerce_website 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
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
Executive Summary

This vulnerability is a SQL injection flaw found in the Ecommerce Website V1.0 application, specifically in the file /ecommerce-website-php/customer/my_account.php?edit_account.

It occurs because the 'c_name' parameter in a POST request is not properly validated, allowing attackers to inject malicious SQL queries.

This can lead to unauthorized access to the database, data tampering, leakage of sensitive information, and potentially full system compromise.

Detection Guidance

This SQL injection vulnerability exists in the 'c_name' parameter of a POST request to /ecommerce-website-php/customer/my_account.php?edit_account. Detection can be performed by monitoring for suspicious POST requests containing SQL injection payloads targeting the 'c_name' parameter.

You can use web application firewall (WAF) logs or intrusion detection systems (IDS) to identify such attempts.

Example commands to detect potential exploitation attempts include using tools like curl or grep to analyze logs or test the endpoint:

  • Use curl to send a test POST request with a common SQL injection payload to check if the system is vulnerable: curl -X POST -d "c_name=' OR '1'='1" https://yourdomain.com/ecommerce-website-php/customer/my_account.php?edit_account
  • Search web server logs for suspicious patterns related to the 'c_name' parameter: grep "c_name=" /var/log/apache2/access.log | grep -E "('|--|;|OR|AND)"
  • Use an automated vulnerability scanner that supports SQL injection detection against the specified URL and parameter.
Mitigation Strategies

Immediate mitigation steps include implementing proper input validation and sanitization on the 'c_name' parameter to prevent SQL injection.

Specifically, the vendor has been advised to use prepared statements (parameterized queries) to safely handle user input.

Additionally, consider deploying a web application firewall (WAF) to block malicious requests targeting this vulnerability.

If possible, restrict access to the vulnerable endpoint or disable the affected functionality until a patch is applied.

Compliance Impact

The SQL injection vulnerability in the Ecommerce Website V1.0 allows unauthorized database access, data tampering, and sensitive information leakage. Such security weaknesses can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.

Failure to mitigate this vulnerability could result in exposure of personal data, violating data protection requirements and potentially leading to legal and financial consequences under these regulations.

Impact Analysis

The vulnerability can have serious impacts including unauthorized database access, which may result in data tampering and leakage of sensitive information.

It can also lead to potential system compromise, threatening system security and business continuity.

Chat Assistant

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

EPSS Chart