CVE-2025-5369: SourceCodester PHP Display Username After Login · SQL Injection
Affects SourceCodester PHP Display Username After LoginSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 08:30 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:NExploitation evidence
Disclosed: evidence found.
CVE published 31 May 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SourceCodester PHP Display Username After Login | Affected
| Fixed in– |
AI-suggested
Since no official patches are available, European organizations should implement the following specific mitigations: 1) Immediately audit all instances of SourceCodester PHP Display Username After Login 1.0 and isolate or take offline any exposed systems until mitigations are applied. 2) Apply input validation and parameterized queries or prepared statements in the /login.php script to sanitize the 'Username' parameter, preventing injection. 3) Employ Web Application Firewalls (WAFs) with rules specifically targeting SQL injection patterns to block malicious payloads targeting this vulnerability. 4) Restrict database user permissions to the minimum necessary to limit the impact of any injection. 5) Monitor web server and database logs for unusual queries or access patterns indicative of exploitation attempts. 6) Consider migrating to alternative, actively maintained authentication modules or frameworks with secure coding practices. 7) Educate development and security teams about secure coding and the risks of SQL injection to prevent similar vulnerabilities in custom code.
Description
A vulnerability classified as critical has been found in SourceCodester PHP Display Username After Login 1.0. Affected is an unknown function of the file /login.php. The manipulation of the argument Username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.