Skip to main content
CVE-2025-7167VulnerabilityPublished

CVE-2025-7167: 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

1. Immediate mitigation should include implementing input validation and parameterized queries or prepared statements in the /category.php file to prevent SQL Injection. 2. If source code modification is not feasible immediately, deploying a Web Application Firewall (WAF) with rules to detect and block SQL Injection attempts targeting the 'ID' parameter can reduce risk. 3. Conduct a thorough audit of database permissions to ensure the application uses the least privilege principle, limiting the potential impact of any injection. 4. Monitor web server and application logs for suspicious query patterns or repeated access attempts to /category.php with unusual parameter values. 5. Engage with the vendor or community to obtain or develop an official patch and apply it promptly once available. 6. Consider isolating or restricting access to the vulnerable application if it hosts sensitive data, until a fix is applied. 7. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in code-projects Responsive Blog Site 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /category.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…