LiveActive security incident?Get immediate response
CVE Record

CVE-2026-15490: RafyMrX TOKO-ONLINE-ROTI add.php sql injection

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-15490 is a SQL injection in RafyMrX TOKO-ONLINE-ROTI. A remote attacker may manipulate product/customer parameters in proses/add.php to affect the database. Public exploit material is reported, but the sources do not show confirmed active exploitation or a vendor patch.

Executive priority

Treat as high priority for any public deployment. Public exploit availability and possible database impact justify rapid triage, access reduction, and vendor guidance review. If the product is not used, record non-exposure and monitor for new information.

Technical view

The issue affects unknown functionality in proses/add.php. Manipulation of kode_produk or kd_cs can cause SQL injection. VulDB lists CVSS 2.0 score 7.5, AV:N/AC:L/Au:N/C:P/I:P/A:P. The affected state is described as up to commit ddfe1cd587be0a0b5135d8b6e85cce2ec3aece99, with rolling-release versioning unavailable.

Likely exposure

Exposure is most relevant for internet-accessible TOKO-ONLINE-ROTI deployments using the affected codebase or unknown rolling-release state. Systems exposing proses/add.php should be prioritized. Asset discovery may be difficult because formal affected release versions are not available.

Exploitation context

The source bundle says an exploit has been released publicly and may be used. It does not cite CISA KEV listing or confirmed active exploitation. Remote reachability and low attack complexity increase practical risk if the application is deployed publicly.

Researcher notes

Evidence is mainly from VulDB and CVE records. The vulnerable function is not named, and rolling-release practices leave version boundaries unclear. Vendor reportedly did not respond. Avoid assuming a patch exists; verify code changes directly before closing remediation.

Mitigation direction

  • Check the project repository or vendor channels for updated guidance or commits.
  • Restrict public access to the application until exposure is understood.
  • Review and harden database permissions used by the web application.
  • Apply input validation and parameterized database queries if maintaining a fork.
  • Monitor application and database logs for suspicious add.php activity.

Validation and detection

  • Inventory deployments of RafyMrX TOKO-ONLINE-ROTI.
  • Determine whether code is at or before commit ddfe1cd587be0a0b5135d8b6e85cce2ec3aece99.
  • Identify whether proses/add.php is reachable from untrusted networks.
  • Review handling of kode_produk and kd_cs for unsafe SQL construction.
  • Check logs for abnormal requests involving proses/add.php parameters.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-15490 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
0ADP providers
5Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 2.0HighAV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR106.4VulDB
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R3.93.4VulDB
7.3CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R3.93.4VulDB
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDB

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-15490Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RafyMrXTOKO-ONLINE-ROTIddfe1cd587be0a0b5135d8b6e85cce2ec3aece99Listed
Weakness

CWE details

CWE-74CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.