Online Railway Reservation SystemApplication · Online Railway Reservation System Project

CVE-2022-33061

HIGH · 7.2 CVSS v3.1 Published 2022-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
Online Railway Reservation System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_service.

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 · high confidence

SQL injection vulnerability in the Online Railway Reservation System v1.0 allows remote attackers to inject malicious SQL code through the id parameter in the delete_service function at /classes/Master.php. The unsanitized input is directly used in SQL queries, enabling data exfiltration, modification, or deletion.

MitigationImplement parameterized queries (prepared statements) for all database operations in Master.php, specifically validating and escaping the id parameter in the delete_service function before using it in SQL queries.

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 Railway Reservation 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm the application version
    Locate and inspect the application's version identifier - check for version files, headers, or the index page source for 'Online Railway Reservation System v1.0'
    Affected if The installed version is exactly 1.0 (Online Railway Reservation System)
  2. Verify Master.php exists
    Check for the presence of /classes/Master.php in the web root directory
    Affected if The file /classes/Master.php exists in the application directory
  3. Locate the delete_service function
    Open /classes/Master.php and search for the function definition 'function delete_service'
    Affected if The delete_service function exists in Master.php
  4. Inspect the id parameter handling
    Within the delete_service function, examine how the 'id' parameter is used - look for direct inclusion in SQL query strings without sanitization functions (such as mysqli_real_escape_string, prepared statements, or parameter binding)
    Affected if The id parameter is concatenated directly into SQL queries without escaping, binding, or validation
  5. Test the delete_service endpoint
    If the application is running, send a request to the delete_service function (typically via POST to the Master.php class handler) with a test id value containing SQL syntax (e.g., id=1' OR '1'='1) and observe the response for SQL syntax errors or unexpected behavior
    Affected if The application returns SQL error messages or executes the injected logic, confirming the injection point is reachable

If the system is Online Railway Reservation System v1.0 and the delete_service function in /classes/Master.php uses the id parameter directly in SQL queries without sanitization, the environment is affected by this CVE.

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 parameterized queries (prepared statements) for all database operations in Master.php, specifically validating and escaping the id parameter in the delete_service function before using it in SQL queries.

Fix this in Online Railway Reservation 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-2022-33061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2022-33061 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