Skip to main content
CVE-2025-7166VulnerabilityPublished

CVE-2025-7166: code-projects Responsive Blog Site · SQL Injection

Affects code-projects Responsive Blog 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.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 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
code-projects Responsive Blog SiteAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should immediately implement the following specific mitigations: 1) Apply Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'ID' parameter in /single.php requests. 2) Restrict database user permissions associated with the blog site to the minimum necessary, preventing unauthorized data modification or extraction. 3) Conduct thorough input validation and sanitization on all user-supplied parameters, especially 'ID', to prevent injection attacks. 4) Monitor web server and database logs for unusual query patterns or repeated failed attempts targeting the vulnerable parameter. 5) If feasible, isolate the blog site in a segmented network zone to limit lateral movement in case of compromise. 6) Plan and prioritize upgrading to a patched or newer version of the Responsive Blog Site once available. 7) Educate web administrators about the vulnerability and encourage rapid incident response readiness.

Description

A vulnerability was found in code-projects Responsive Blog Site 1.0. It has been classified as critical. This affects an unknown part of the file /single.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…