dbcve.org
Vehicle Record Management SystemApplication · Anujk305

CVE-2025-44182

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Phpgurukul Vehicle Record Management System v1.0 is vulnerable to Cross Site Scripting (XSS) via the vehiclename, modelnumber, regnumber, vehiclesubtype, chasisnum, enginenumber' in the /admin/edit-vehicle.php component. This allows attackers to execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in Phpgurukul Vehicle Record Management System v1.0 allows authenticated attackers to inject malicious JavaScript through multiple input fields (vehiclename, modelnumber, regnumber, vehiclesubtype, chasisnum, enginenumber) in the /admin/edit-vehicle.php admin panel page. The unsanitized input is stored in the database and executed when other users view the vehicle records.

MitigationImplement input validation and output encoding/escaping for all user-supplied data in edit-vehicle.php. Apply context-appropriate encoding when displaying vehicle data and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vehicle Record Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Phpgurukul Vehicle Record Management System is installed
    Locate the application files on the web server. Look for directories containing PHP files related to vehicle management, typically in the web root. Check for files named 'edit-vehicle.php' or similar vehicle management scripts.
    Affected if The application is present and matches version 1.0 from Anujk305
  2. Verify the admin panel endpoint exists
    Access the URL path /admin/edit-vehicle.php through the web browser or curl command to confirm the vulnerable page exists and is accessible.
    Affected if The /admin/edit-vehicle.php page returns a valid HTTP response (200 OK) indicating the vulnerable script is present
  3. Confirm admin authentication is possible
    Attempt to log into the admin panel. Check if default credentials work or if you have valid admin credentials. The vulnerability requires an authenticated attacker.
    Affected if You can authenticate to the admin panel at /admin/ or similar admin login page
  4. Check for stored XSS in vehicle record fields
    If you have database access, query the vehicle records table for any HTML or script tags in fields: vehiclename, modelnumber, regnumber, vehiclesubtype, chasisnum, enginenumber. Use SQL like: SELECT * FROM vehicles WHERE vehiclename LIKE '%<script%' OR modelnumber LIKE '%script%'
    Affected if Database contains unsanitized script tags or JavaScript event handlers in any of the six affected vehicle fields
  5. Inspect the edit-vehicle.php source code
    Open /admin/edit-vehicle.php in a text editor and search for the six input fields (vehiclename, modelnumber, regnumber, vehiclesubtype, chasisnum, enginenumber). Check if they are used in SQL queries or displayed without sanitization functions like htmlspecialchars()
    Affected if The code shows direct insertion of these POST/GET parameters into the database or direct output without encoding

You are affected if the Vehicle Record Management System v1.0 is installed and the edit-vehicle.php admin page exists with any stored XSS payloads present in the vehicle record database fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding/escaping for all user-supplied data in edit-vehicle.php. Apply context-appropriate encoding when displaying vehicle data and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Fix this in Vehicle Record Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-44182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-44182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data