CVE-2026-14639
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in CodeAstro Ecommerce Website 1.0 allows remote attackers to inject malicious SQL queries through the c_name parameter in /ecommerce-website-php/customer/my_account.php when editing account details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the CodeAstro Ecommerce Website installationSearch your web server document root for the 'ecommerce-website-php' directory, or check if /ecommerce-website-php/customer/my_account.php exists on the server.Affected if The directory /ecommerce-website-php exists and contains the my_account.php file.
-
Confirm the product versionCheck for a version file or header in the installation directory, such as a readme.txt, version.php, or admin panel that displays the software version.Affected if The installed version is CodeAstro Ecommerce Website 1.0.
-
Inspect the vulnerable file for the SQL injection pointOpen /ecommerce-website-php/customer/my_account.php in a text editor and search for occurrences of 'c_name' within SQL query strings (typically using $c_name in SELECT, UPDATE, or INSERT statements).Affected if The file contains SQL queries that directly incorporate the c_name parameter without visible sanitization or prepared statements.
-
Verify the account editing functionality is accessibleLog into the ecommerce site as a customer user, navigate to the account settings or 'my account' section, and locate the form that allows editing the name field.Affected if The customer account editing form is accessible and submits the c_name parameter to my_account.php.
-
Test for unsanitized input in the c_name parameterUse a web proxy or browser developer tools to intercept the account update request and observe whether the c_name value is sent directly to the server without apparent parameterization in the request.Affected if The c_name parameter is submitted as a plain text value in the HTTP request without evidence of parameterized query handling.
Your environment is affected if CodeAstro Ecommerce Website version 1.0 is installed and the /ecommerce-website-php/customer/my_account.php file exists with the c_name parameter being used in dynamic SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with prepared statements/parameterized queries to properly sanitize the c_name input before database execution.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14639 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data