CVE-2025-7929: code-projects Church Donation System · SQL Injection
Affects code-projects Church Donation SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% 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 21 Jul 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 |
|---|---|---|
| code-projects Church Donation System | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include: 1) Conducting a thorough audit of all input parameters in the Church Donation System, especially those related to member editing functions, to identify and remediate SQL injection points. 2) Applying input validation and parameterized queries (prepared statements) to eliminate direct SQL injection vectors. 3) If source code modification is not feasible immediately, deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'fname' parameter and related inputs. 4) Restricting network access to the application to trusted IP ranges where possible, reducing exposure. 5) Monitoring logs for suspicious database errors or anomalous query patterns indicative of exploitation attempts. 6) Planning for an urgent update or patch deployment once available from the vendor or considering migration to a more secure donation management platform. 7) Educating staff about the vulnerability and potential phishing or social engineering attacks that could leverage this flaw. 8) Ensuring regular backups of the database to enable recovery in case of data tampering or loss. These steps go beyond generic advice by focusing on immediate protective controls and operational readiness until a vendor patch is released.
Description
A vulnerability was found in code-projects Church Donation System 1.0. It has been classified as critical. Affected is an unknown function of the file /members/edit_Members.php. The manipulation of the argument fname leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.