CVE-2018-25385: E-Registrasi Pencak Silat 18.10 SQL Injection via id_partai
E-Registrasi Pencak Silat 18.10 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the id_partai parameter. Attackers can send GET requests to monitor_nilai.php with crafted SQL payloads in the id_partai parameter to extract sensitive database information including admin credentials and user data.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated person reach the application and manipulate database queries. For an affected tournament registration site, the main business risk is exposure of administrator credentials and participant or user data. The product appears niche, so urgency depends on whether version 18.10 is deployed and reachable.
Executive priority
Prioritize quickly if this software is deployed, because the vulnerability is unauthenticated and can expose sensitive database records. If the product is not present, no direct action is needed beyond documenting non-exposure.
Technical view
CVE-2018-25385 is CWE-89 SQL injection in E-Registrasi/Registrasi Pencak Silat 18.10, tied to the id_partai parameter in monitor_nilai.php. The CVSS 4.0 score is 8.8, with network access, low complexity, no privileges, no user interaction, high confidentiality impact, and low integrity impact.
Likely exposure
Exposure is limited to organizations running Registrasi Pencak Silat 18.10, especially if the application is internet-facing. The source bundle provides no CPEs and no deployment prevalence data, so asset confirmation is required.
Exploitation context
The bundle cites an ExploitDB entry, so public exploit information exists. It does not cite CISA KEV listing or any active exploitation reporting. Treat this as a publicly documented unauthenticated SQL injection, not confirmed in-the-wild exploitation.
Researcher notes
Evidence supports a high-risk SQL injection with public exploit reference, but the bundle does not name a vendor patch, workaround, CPE, or active exploitation. Validation should focus on product/version presence, reachability, and database query handling.
Mitigation direction
Check vendor or project guidance for any fixed release or official workaround.
Remove public internet exposure until the application is validated or remediated.
Restrict access to trusted networks if the service must remain online.
Use parameterized database queries if maintaining or patching the application code.
Rotate administrator credentials if exposure or compromise is suspected.
Validation and detection
Inventory web applications for Registrasi Pencak Silat version 18.10.
Confirm whether monitor_nilai.php is reachable from untrusted networks.
Review application code for unsafe SQL construction around id_partai.
Review web and database logs for unusual access to affected pages.
Verify administrator and user data were not exposed if suspicious activity exists.
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 · 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.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.