Skip to main content
CVE-2025-7756VulnerabilityPublished

CVE-2025-7756: code-projects E-Commerce Site · Cross-Site Request Forgery

Affects code-projects E-Commerce SiteSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 22% 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 17 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubbalancelee/CVEpkg:github/balancelee/CVEOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, European organizations should implement specific mitigations to reduce risk: 1) Implement anti-CSRF tokens in all state-changing requests to ensure that requests originate from legitimate users and sessions. 2) Enforce SameSite cookie attributes (preferably 'Strict' or 'Lax') to limit cookie transmission in cross-site requests. 3) Educate users about phishing and social engineering tactics to minimize the likelihood of user interaction triggering the exploit. 4) Monitor web application logs for unusual or unexpected requests that could indicate exploitation attempts. 5) If possible, upgrade to a newer, patched version of the e-commerce platform once available or consider alternative platforms with active security support. 6) Employ web application firewalls (WAF) with rules tailored to detect and block CSRF attack patterns. 7) Conduct regular security assessments and penetration testing focusing on CSRF and related web vulnerabilities to proactively identify and remediate weaknesses.

Description

A vulnerability classified as problematic has been found in code-projects E-Commerce Site 1.0. Affected is an unknown function. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…