Skip to main content
CVE-2025-13247VulnerabilityPublished Updated

CVE-2025-13247: PHPGurukul Tourism Management System · SQL Injection

Affects PHPGurukul Tourism Management SystemSource 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 35% 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 16 Nov 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
PHPGurukul Tourism Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediately restrict access to the /admin/user-bookings.php endpoint to trusted IP addresses or internal networks using firewall rules or web server access controls. 2. Implement strong input validation and parameterized queries (prepared statements) in the uid parameter handling to prevent SQL injection. 3. Conduct a thorough code review of the entire application to identify and remediate similar injection flaws. 4. Monitor web server and database logs for unusual queries or error messages indicative of injection attempts. 5. If possible, isolate the affected system from the internet or place it behind a VPN until a patch is available. 6. Engage with PHPGurukul or the software vendor to obtain or request an official patch or update. 7. Educate administrators and developers about secure coding practices and the risks of SQL injection. 8. Consider deploying a Web Application Firewall (WAF) with rules to detect and block SQL injection payloads targeting the uid parameter. 9. Regularly back up databases and verify backup integrity to enable recovery in case of data tampering. 10. Plan for an incident response strategy to quickly address any exploitation attempts.

Description

A security flaw has been discovered in PHPGurukul Tourism Management System 1.0. The affected element is an unknown function of the file /admin/user-bookings.php. The manipulation of the argument uid results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks.

References

Community reviews

Loading reviews…