Skip to main content
VulnerabilityPublished

CVE-2026-14800: imhamzaazam ecommerceFlask · Cross-Site Request Forgery

Affects imhamzaazam ecommerceFlaskSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
imhamzaazamecommerceFlaskAffected
  • =cb7d9e24c30a99379651b7493b32048126ef402b
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:imhamzaazam:ecommerceflask:*:*:*:*:*:*:*:*

AI-suggested

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.

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.

References

Community reviews

Loading reviews…