dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15489

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 vulnerability was identified in RafyMrX TOKO-ONLINE-ROTI up to ddfe1cd587be0a0b5135d8b6e85cce2ec3aece99. Affected by this vulnerability is an unknown functionality of the file proses/login.php. The manipulation of the argument Username leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. 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 · moderate confidence

SQL injection vulnerability in RafyMrX TOKO-ONLINE-ROTI's proses/login.php allows remote attackers to inject malicious SQL queries via the Username parameter. The vulnerability is exploitable without authentication and a public exploit exists.

MitigationImplement parameterized queries/prepared statements for the Username parameter and all user inputs in the login functionality. Review and sanitize all other input-handling code in the application for similar SQL injection flaws.

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. Identify if TOKO-ONLINE-ROTI application is present
    Search the system for files or directories named 'TOKO-ONLINE-ROTI' or 'RafyMrX'. Use file system search commands like 'find / -type d -name "TOKO-ONLINE-ROTI"' or check web server document roots for this application folder.
    Affected if The application is installed on the system
  2. Locate the vulnerable login script
    Look for the file 'proses/login.php' within the TOKO-ONLINE-ROTI application directory structure. Common paths may include 'proses/login.php' or 'include/proses/login.php' under the web root.
    Affected if The file proses/login.php exists in the application
  3. Verify the application is network accessible
    Check if the application is deployed on a web server and reachable via HTTP/HTTPS. Attempt to access the login page directly through a browser or curl request to the suspected URL.
    Affected if The application is accessible over the network (not localhost-only or firewalled)
  4. Inspect the Username parameter handling in login.php
    Open proses/login.php and locate the code handling the 'Username' or 'username' POST/GET parameter. Check how this input is used in SQL queries - look for string concatenation or direct insertion into SQL statements without prepared statements.
    Affected if The code directly incorporates the Username parameter into SQL queries without using parameterized queries or input sanitization
  5. Confirm lack of prepared statements in login logic
    Search the proses/login.php file for 'prepare', 'bindParam', 'bindValue', or '$stmt' statements. Verify that SQL queries are constructed using string concatenation with user input.
    Affected if No prepared statements or parameter binding are used for the login SQL queries

The environment is affected if the TOKO-ONLINE-ROTI application is installed with the proses/login.php file present and the code shows direct use of the Username parameter in SQL queries without prepared statements.

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 the Username parameter and all user inputs in the login functionality. Review and sanitize all other input-handling code in the application for similar SQL injection flaws.

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-15489 — 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-15489 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