dbcve.org
Billing SoftwareApplication · Kashipara

CVE-2024-0492

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability classified as critical was found in Kashipara Billing Software 1.0. Affected by this vulnerability is an unknown functionality of the file buyer_detail_submit.php of the component HTTP POST Request Handler. The manipulation of the argument gstn_no leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250597 was 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 · high confidence

SQL injection vulnerability in Kashipara Billing Software 1.0's buyer_detail_submit.php script. The gstn_no parameter in HTTP POST requests is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement prepared statements/parameterized queries for all database operations involving the gstn_no parameter. Additionally, apply input validation and output encoding. Conduct a full code audit to identify and remediate other SQL injection vulnerabilities in the application.

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
Billing SoftwareApplication
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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Kashipara Billing Software is installed
    Search the web root directory for files named 'buyer_detail_submit.php' or look for the application's main files. Common paths may include /admin/, /billing/, or the web root.
    Affected if The file buyer_detail_submit.php exists in the application directory and the software is Kashipara Billing Software version 1.0
  2. Confirm the software version
    Locate the version identifier in the application's main files (often in index.php, about.php, README, or a config file). Compare the version number to '1.0'.
    Affected if The installed version is exactly 1.0 (note: other versions may not be affected by this specific CVE)
  3. Check if the buyer_detail_submit.php script processes POST requests
    Inspect the buyer_detail_submit.php file and look for $_POST['gstn_no'] usage in the code. Search for database query functions like mysqli_query, mysql_query, PDO query, or similar.
    Affected if The script contains $_POST or $_REQUEST references to 'gstn_no' and includes database query operations without visible prepared statement usage
  4. Examine database query construction for gstn_no
    Review the buyer_detail_submit.php source code around the gstn_no parameter. Look for direct string concatenation or interpolation of this parameter into SQL queries (e.g., "SELECT ... WHERE gstn_no = '" . $_POST['gstn_no'] . "'").
    Affected if The gstn_no parameter appears to be directly inserted into SQL queries without using parameterized queries or input sanitization functions
  5. Verify application has network accessibility
    Confirm the web server is running and the buyer_detail_submit.php endpoint is accessible via HTTP/HTTPS. Test by sending a benign POST request with a test gstn_no value to the endpoint.
    Affected if The script is accessible over the network and accepts POST requests to the buyer_detail_submit.php endpoint

The environment is affected if Kashipara Billing Software version 1.0 is installed, buyer_detail_submit.php exists with the gstn_no parameter being used in unsanitized SQL queries.

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 prepared statements/parameterized queries for all database operations involving the gstn_no parameter. Additionally, apply input validation and output encoding. Conduct a full code audit to identify and remediate other SQL injection vulnerabilities in the application.

Fix this in Billing Software 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-2024-0492 — 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-2024-0492 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