CVE-2018-25431: No-Cms 1.0 SQL Injection via order_by Parameter
No-Cms 1.0 contains an SQL injection vulnerability in the order_by parameter of the manage_privilege export endpoint that allows authenticated attackers to manipulate database queries. Attackers can submit POST requests to /nocms/main/manage_privilege/index/export with malicious SQL code in the order_by[0] parameter to extract sensitive database information.
Security readout for executives and security teams
Plain-English summary
No-CMS 1.0 has an authenticated SQL injection flaw in an administrative export function. A user with low privileges could manipulate database queries and potentially read sensitive database information. The issue is high severity, but the provided sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Prioritize within the next security remediation cycle, sooner if No-CMS is internet-facing or stores sensitive data. The business risk is data exposure through an authenticated web application flaw with public exploit information available.
Technical view
CVE-2018-25431 is CWE-89 SQL injection in the manage_privilege export endpoint through the order_by[0] parameter. The CVSS 4.0 score is 7.1, with network access, low attack complexity, low privileges required, and no user interaction. Impact is primarily confidentiality, with limited integrity impact.
Likely exposure
Exposure is likely limited to organizations running goFrendiAsgard No-CMS 1.0 with authenticated users able to access the manage_privilege export route. Public internet exposure raises urgency, but authentication is required according to the provided advisory data.
Exploitation context
ExploitDB is cited, indicating public exploit information exists. The source bundle does not indicate CISA KEV status or confirmed active exploitation. Treat exploitability as credible, but do not claim active attacks without additional evidence.
Researcher notes
The provided sources name No-CMS 1.0 only. No official patch, mitigation, or active exploitation evidence is included in the bundle. Focus research on confirming affected version, privilege boundaries, endpoint reachability, and whether vendor code constrains order_by inputs.
Mitigation direction
Identify and inventory any No-CMS 1.0 deployments.
Check vendor or maintainer guidance for a fixed release or official workaround.
Restrict access to administrative and export routes to trusted users and networks.
Review role permissions for accounts that can access manage_privilege export functions.
Retire or isolate No-CMS 1.0 if no supported fix is available.
Validation and detection
Confirm whether No-CMS 1.0 is deployed in production or staging.
Verify who can authenticate and reach the manage_privilege export endpoint.
Review logs for unusual authenticated export activity or order_by parameter anomalies.
Check whether sorting parameters are allow-listed and safely handled server-side.
Validate only in an approved test environment using non-destructive methods.
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.