Skip to main content
CVE-2025-6845VulnerabilityPublished Updated

CVE-2025-6845: code-projects Simple Forum · SQL Injection

Affects code-projects Simple ForumSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jun 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 Simple ForumAffected
  • =1.0
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'User' parameter in /register1.php. 2) Conduct thorough input validation and sanitization on all user-supplied data, especially the 'User' argument, using parameterized queries or prepared statements if modifying the source code is possible. 3) Restrict database user permissions to the minimum necessary, preventing unauthorized data manipulation even if injection occurs. 4) Monitor web server and database logs for suspicious activities indicative of SQL injection attempts. 5) Consider isolating or disabling the vulnerable registration functionality temporarily if feasible. 6) Plan and prioritize upgrading to a patched or newer version of the forum software once available. 7) Educate IT and security teams about this vulnerability and ensure incident response plans include detection and mitigation of SQL injection attacks.

Description

A vulnerability was found in code-projects Simple Forum 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /register1.php. The manipulation of the argument User leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…