CVE-2025-8971 is a SQL injection vulnerability in itsourcecode Online Tour and Travel Management System 1.0. It affects unspecified code in the administrative travellers.php endpoint, where manipulation of the val-username argument can inject SQL statements. The attack can be initiated remotely, and a public exploit has been disclosed.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a C-language exploit for CVE-2025-8971, a SQL injection vulnerability in the itsourcecode Online Tour and Travel Management System 1.0. The main file, script.c, implements the exploit logic: it constructs HTTP POST requests to the vulnerable endpoint /admin/operations/travellers.php, injecting SQL payloads into the val-username parameter. The exploit supports both time-based blind SQL injection (using payloads like SLEEP(3)) and optional file upload (e.g., a PHP webshell) to achieve remote code execution if the vulnerability is confirmed. The script is configurable via command-line arguments for the target URL, cookies, fake IP, file upload, and verbosity. The README provides compilation and usage instructions, as well as example output. The repository is operational in maturity, providing both vulnerability verification and exploitation capabilities. No hardcoded credentials or IPs are present, but the endpoint and parameter are clearly fingerprintable.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.