CVE-2025-6472: code-projects Online Bidding System · SQL Injection
Affects code-projects Online Bidding SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubganzhi-qcy/cvepkg:github/ganzhi-qcy/cveOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate mitigation should include implementing input validation and parameterized queries or prepared statements in the /showprod.php file to prevent SQL injection. 2. If source code modification is not feasible immediately, deploy Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'ID' parameter. 3. Conduct thorough code audits of the entire application to identify and remediate similar injection points. 4. Restrict database user privileges to the minimum necessary to limit the impact of potential injection attacks. 5. Monitor application logs and database logs for unusual query patterns or errors indicative of exploitation attempts. 6. Engage with the vendor or community to obtain or develop patches or updates addressing this vulnerability. 7. Implement network segmentation to isolate the bidding system from critical internal networks. 8. Educate development and security teams on secure coding practices to prevent recurrence. 9. Plan for incident response readiness in case exploitation occurs, including data backup and recovery procedures.
Description
A vulnerability, which was classified as critical, has been found in code-projects Online Bidding System 1.0. Affected by this issue is some unknown functionality of the file /showprod.php. The manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.