dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15490

HIGH · 7.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 security flaw has been discovered in RafyMrX TOKO-ONLINE-ROTI up to ddfe1cd587be0a0b5135d8b6e85cce2ec3aece99. Affected by this issue is some unknown functionality of the file proses/add.php. The manipulation of the argument kode_produk/kd_cs results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

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 proses/add.php of the TOKO-ONLINE-ROTI application allows remote attackers to inject malicious SQL queries via the kode_produk/kd_cs parameters. The lack of input sanitization or parameterized queries in the affected PHP file enables database compromise.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly in proses/add.php, and perform input validation on all user-supplied parameters before using them in SQL queries.

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

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
Low
Integrity
Low
Availability
Low

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

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. Locate the TOKO-ONLINE-ROTI application installation
    Search the web server document root for a directory or file structure containing the string 'toko-online-roti' or check known PHP application paths for the presence of proses/add.php
    Affected if The application directory structure is found on the server
  2. Verify the presence of the vulnerable file
    Confirm that the file proses/add.php exists within the application directory
    Affected if The file proses/add.php exists in the installation
  3. Examine kode_produk and kd_cs parameter handling
    Open proses/add.php and inspect how the kode_produk and kd_cs parameters are used in SQL queries - look for direct string concatenation or lack of prepared statements/parameter binding
    Affected if The code shows direct insertion of kode_produk or kd_cs variables into SQL queries without parameterized queries or input sanitization functions (such as mysqli_prepare, PDO::prepare, or htmlspecialchars/escaping)
  4. Check for input validation mechanisms
    Review proses/add.php to determine if any input validation, sanitization, or filtering is performed on kode_produk and kd_cs before their use in SQL statements
    Affected if No input validation or sanitization is performed on these parameters prior to SQL execution
  5. Compare application version if determinable
    Check for a version identifier in any configuration files, README, or composer.json within the application root
    Affected if The installed version matches or predates any known version of TOKO-ONLINE-ROTI containing this vulnerability

The environment is affected if the TOKO-ONLINE-ROTI application is installed and the proses/add.php file contains direct SQL query construction using kode_produk or kd_cs parameters without parameterized queries or input sanitization.

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, particularly in proses/add.php, and perform input validation on all user-supplied parameters before using them in SQL queries.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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