Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2024-48246: Stored XSS in Vehicle Management System 1.0 booking.php

Published Mar 5, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.4Medium · v3.1
EPSS0.43%38th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
JanobeSourcecodester
IdentifiersCVE-2024-48246CWE-79 · Improper Neutralization of Input…

Vehicle Management System 1.0 is vulnerable to a stored cross-site scripting (XSS) attack via the "Name" parameter in /vehicle-management/booking.php. User-supplied input is not properly sanitized before being stored and rendered, allowing attackers to inject arbitrary JavaScript code that will execute in the context of users viewing the affected page.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to execute arbitrary JavaScript in the browser of users who view the affected booking page, potentially leading to session hijacking, credential theft, or further attacks against users of the system.

Mitigation

If you can’t patch tonight, do this now.

Restrict input to the "Name" parameter to only allow safe characters, implement Content Security Policy (CSP) headers to reduce the impact of XSS, and educate users to avoid clicking on suspicious links. Monitor and audit user input for signs of exploitation until a patch is applied.

Remediation

Patch, then assume compromise.

Sanitize and properly encode all user-supplied input in the "Name" parameter before storing or rendering it. Apply output encoding when displaying user input and consider using security libraries or frameworks that provide built-in XSS protection. Update to a patched version if available.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JanobeVehicle Management Systemapplication
SourcecodesterVehicle Management Systemapplication
FAQ

Frequently asked questions

Is CVE-2024-48246 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2024-48246 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-48246?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2024-48246.
Is there a patch for CVE-2024-48246?
Sanitize and properly encode all user-supplied input in the "Name" parameter before storing or rendering it. Apply output encoding when displaying user input and consider using security libraries or frameworks that provide built-in XSS protection.
What products are affected by CVE-2024-48246?
Janobe Vehicle Management System and Sourcecodester Vehicle Management System.
How severe is CVE-2024-48246?
CVE-2024-48246 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.43% (38th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.