CVE-2026-14800: Cross-Site Request Forgery in imhamzaazam ecommerceFlask
A weakness has been identified in imhamzaazam ecommerceFlask up to cb7d9e24c30a99379651b7493b32048126ef402b. The affected element is an unknown function. This manipulation causes cross-site request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.
AI Analysis
Technical Summary
CVE-2026-14800 describes a cross-site request forgery (CSRF) vulnerability in the imhamzaazam ecommerceFlask project affecting all code up to commit cb7d9e24c30a99379651b7493b32048126ef402b. The vulnerability arises from an unspecified function that does not properly protect against CSRF attacks, allowing remote attackers to trick authenticated users into submitting unwanted requests. The project follows a rolling release model, so no discrete version numbers are available. The vulnerability was disclosed publicly, but the vendor has not yet provided a patch or official remediation guidance.
Potential Impact
Successful exploitation of this CSRF vulnerability could allow remote attackers to induce authenticated users to perform unintended actions on the ecommerceFlask application. This could lead to unauthorized state changes or transactions within the application. The CVSS 4.0 base score of 5.3 (medium severity) reflects the network attack vector, low attack complexity, no privileges required, and user interaction required, with limited impact on confidentiality and integrity and no impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded or issued a fix, users should monitor the project repository for updates. In the meantime, implementing standard CSRF protections such as anti-CSRF tokens and validating the origin of requests may help mitigate risk.
CVE-2026-14800: Cross-Site Request Forgery in imhamzaazam ecommerceFlask
Description
A weakness has been identified in imhamzaazam ecommerceFlask up to cb7d9e24c30a99379651b7493b32048126ef402b. The affected element is an unknown function. This manipulation causes cross-site request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.
CVSS v4.0
Score 5.3medium
Affected software
cpe:2.3:a:imhamzaazam:ecommerceflask:*:*:*:*:*:*:*:*AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-14800 describes a cross-site request forgery (CSRF) vulnerability in the imhamzaazam ecommerceFlask project affecting all code up to commit cb7d9e24c30a99379651b7493b32048126ef402b. The vulnerability arises from an unspecified function that does not properly protect against CSRF attacks, allowing remote attackers to trick authenticated users into submitting unwanted requests. The project follows a rolling release model, so no discrete version numbers are available. The vulnerability was disclosed publicly, but the vendor has not yet provided a patch or official remediation guidance.
Potential Impact
Successful exploitation of this CSRF vulnerability could allow remote attackers to induce authenticated users to perform unintended actions on the ecommerceFlask application. This could lead to unauthorized state changes or transactions within the application. The CVSS 4.0 base score of 5.3 (medium severity) reflects the network attack vector, low attack complexity, no privileges required, and user interaction required, with limited impact on confidentiality and integrity and no impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded or issued a fix, users should monitor the project repository for updates. In the meantime, implementing standard CSRF protections such as anti-CSRF tokens and validating the origin of requests may help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-07-05T18:36:52.340Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b579327e9c79719f9053a
Added to database: 07/06/2026, 07:21:55 UTC
Last enriched: 07/13/2026, 09:04:18 UTC
Last updated: 08/19/2026, 10:57:07 UTC
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.