dbcve.org
Online Motorcycle \(bike\) Rental SystemApplication · Oretnom23

CVE-2023-5585

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-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
A vulnerability was found in SourceCodester Online Motorcycle Rental System 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file /admin/?page=bike of the component Bike List. The manipulation of the argument Model with the input "><script>confirm (document.cookie)</script> leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-242170 is the identifier assigned to this vulnerability.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in SourceCodester Online Motorcycle Rental System 1.0 within the Bike List component at /admin/?page=bike. The Model parameter fails to sanitize user input, allowing injection of malicious JavaScript payloads such as '><script>confirm(document.cookie)</script>. This allows remote attackers to execute arbitrary scripts in the context of authenticated admin users.

MitigationImplement proper input validation and output encoding for the Model parameter. All user-supplied data should be sanitized before storage and HTML-escaped before rendering. Consider implementing a Content Security Policy (CSP) header as an additional 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
Online Motorcycle \(bike\) Rental 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 the installed application
    Locate the web application files or banner and confirm it is SourceCodester Online Motorcycle Rental System. Check for files like index.php, readme files, or application metadata that identify the product name.
    Affected if The application is SourceCodester Online Motorcycle Rental System and no other motorcycle rental system is in use.
  2. Confirm the application version
    Check the application version through admin panel headers, source code comments, or version files. Compare the installed version against the affected range: version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Verify admin access to bike management
    Navigate to the admin panel and access the Bike List component at /admin/?page=bike. Log in with admin credentials to confirm access.
    Affected if The /admin/?page=bike endpoint is accessible and displays the bike management interface.
  4. Inspect Model parameter for input validation
    In the Bike List component, add or edit a bike entry and locate the Model parameter field. Submit a test payload such as <script>alert('test')</script> in the Model field and save the entry.
    Affected if The Model parameter accepts and stores the raw script tag without sanitization or encoding, and the payload persists and renders when the bike list is displayed.
  5. Verify stored XSS execution
    After saving the entry with the test payload, view the bike list page again. Check if the injected script tag executes or appears unescaped in the rendered HTML.
    Affected if The malicious payload renders as raw HTML/JavaScript in the browser, indicating the XSS vulnerability is present.

A user is affected if they are running SourceCodester Online Motorcycle Rental System version 1.0 and the Model parameter at /admin/?page=bike stores and displays unsanitized input, allowing stored XSS execution.

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 proper input validation and output encoding for the Model parameter. All user-supplied data should be sanitized before storage and HTML-escaped before rendering. Consider implementing a Content Security Policy (CSP) header as an additional defense-in-depth measure.

Fix this in Online Motorcycle \(bike\) Rental System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5585 — 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-2023-5585 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