Loading vulnerability…
TripSpark VEO Transportation-2.2.x-XP_BB-20201123-184084 and NovusEDU-2.2.x-XP_BB-20201123-184084 are vulnerable to SQL injection due to improper sanitization of POST body parameters in the 'Student Busing Information' search functionality. User-supplied data is not properly validated or sanitized on the server side, allowing attackers to inject arbitrary SQL commands into backend queries.
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 is a small proof-of-concept package for CVE-2021-3262, a blind unauthenticated SQL injection affecting TripSpark VEO Transportation / NovusEDU public "Student Busing Information" pages. The repo contains 5 files total: a README with vulnerability narrative and reproduction guidance, plus three PoC artifacts under `poc/` and a `.gitignore`. There is no standalone exploit program; instead, the repository provides a replayable HTTP request, SQL payloads, and sqlmap notes. Core exploit capability: inject SQL into the `editOEN` POST parameter of an ASP.NET WebForms form. Because the target is blind, the PoC focuses on stacked-query execution with two confirmation methods: `waitfor delay` for time-based verification and `master.dbo.xp_dirtree` for out-of-band interaction. The `xp_dirtree` payload forces the SQL Server service account to access an attacker-controlled UNC path (`\\ATTACKER_IP\fro`), producing observable SMB authentication and potentially exposing NTLM material. The repo also includes a time-based privilege oracle using `is_srvrolemember('sysadmin')`. Repository structure and purpose: - `README.md`: full vulnerability description, affected versions, exploitation rationale, impact, remediation, and reproduction steps. - `poc/exploited-request.http`: complete sample POST request with placeholders for `TARGET_HOST`, `ATTACKER_IP`, session cookie, `__VIEWSTATE`, and `__EVENTVALIDATION`; intended for replay or direct use with sqlmap `-r`. - `poc/payloads.sql`: baseline, quote test, time-delay, OOB SMB callback, and privilege-check payloads. - `poc/sqlmap.md`: operational notes for using sqlmap against this blind ASP.NET target, including token refresh guidance. This is a real exploit PoC rather than a detector-only script. However, it is not weaponized software; it is documentation plus payload material intended to demonstrate and reproduce the vulnerability in authorized environments.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.