CVE-2025-6470: 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 26 Oct 2026, 06:26 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Online Bidding System | Affected
| Fixed in– |
AI-suggested
1. Immediate implementation of Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'ID' parameter in /bidlog.php. 2. Conduct thorough input validation and sanitization on all user-supplied parameters, especially the 'ID' argument, using parameterized queries or prepared statements to prevent SQL injection. 3. If source code access is available, refactor the vulnerable code to use secure database access methods and perform rigorous code reviews focusing on input handling. 4. Monitor database logs and application logs for unusual query patterns or repeated failed injection attempts to detect exploitation attempts early. 5. Isolate the bidding system database with strict access controls and limit database user privileges to the minimum necessary to reduce potential damage. 6. Develop and deploy patches or updates as soon as the vendor releases them; meanwhile, consider temporary disabling or restricting access to the vulnerable functionality if feasible. 7. Educate development and security teams about secure coding practices and the risks of SQL injection to prevent similar vulnerabilities in future releases. 8. Perform penetration testing and vulnerability scanning focused on injection flaws to identify and remediate any other potential injection points in the system.
Description
A vulnerability classified as critical has been found in code-projects Online Bidding System 1.0. Affected is an unknown function of the file /bidlog.php. The manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.