CVE-2025-10800: itsourcecode Online Discussion Forum · SQL Injection
Affects itsourcecode Online Discussion ForumSource 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 40% 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 Sep 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 |
|---|---|---|
| itsourcecode Online Discussion Forum | Affected
| Fixed in– |
AI-suggested
Specific mitigation steps include: 1) Immediate upgrade or patching: Since no official patches are currently available, organizations should consider disabling or isolating the vulnerable forum instance until a fix is released. 2) Input validation and parameterized queries: Developers or administrators with access to the source code should implement strict input validation and use prepared statements or parameterized queries to prevent SQL Injection. 3) Web Application Firewall (WAF): Deploy a WAF with rules specifically designed to detect and block SQL Injection attempts targeting the 'email' and 'password' parameters. 4) Monitoring and logging: Enable detailed logging of web requests and database queries to detect suspicious activity indicative of exploitation attempts. 5) Access controls: Restrict database user permissions to the minimum necessary to limit the impact of a successful injection. 6) Incident response readiness: Prepare to respond to potential breaches by having data backup and recovery plans in place. 7) Vendor engagement: Engage with itsourcecode developers or community to encourage timely patch development and dissemination.
Description
A weakness has been identified in itsourcecode Online Discussion Forum 1.0. The impacted element is an unknown function of the file /index.php. Executing manipulation of the argument email/password can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be exploited.