Security readout for executives and security teams
Plain-English summary
Kados R10 GreenBee has an unauthenticated SQL injection in update_release.php. An attacker who can reach the affected page may query backend database data. The sources describe exposure of database user, database name, and DBMS version; broader impact depends on database permissions and stored data.
Executive priority
Treat as high priority if Kados R10 GreenBee is exposed to the internet or stores sensitive operational data. Prioritize containment and vendor guidance because the sources do not identify a confirmed patch.
Technical view
The release_id parameter in boards_buttons/update_release.php is reportedly concatenated into SQL without sanitization, enabling UNION-based SQL injection. CVSS 4.0 is 8.8 high, with network access, low complexity, no privileges, and no user interaction required. CWE-89 applies.
Likely exposure
Exposure is likely limited to organizations running Kados R10 GreenBee with the vulnerable PHP route reachable, especially internet-facing deployments. The provided sources list only Kados R10 GreenBee and provide no CPEs or confirmed fixed versions.
Exploitation context
The bundle references ExploitDB, so public exploit information exists. KEV is false in the provided data, and no cited source states active exploitation. Do not treat this as exploited in the wild without additional evidence.
Researcher notes
Evidence supports unauthenticated SQL injection through release_id and public exploit availability. Evidence is incomplete for vendor patch status, real-world exploitation, affected build granularity, and downstream forks. Avoid assuming other Kados versions are affected.
Mitigation direction
- Check Kados and advisory sources for a fixed release or official mitigation.
- Remove public access to the affected Kados instance where possible.
- Restrict access to trusted networks or authenticated administrative users.
- Use database least privilege to limit impact from query abuse.
- For maintained code, replace unsafe SQL concatenation with parameterized queries.
Validation and detection
- Inventory Kados deployments and confirm whether R10 GreenBee is present.
- Check whether boards_buttons/update_release.php is reachable from untrusted networks.
- Review application code handling release_id for unsafe SQL concatenation.
- Review web and database logs for unusual release_id requests or database errors.
- Confirm compensating controls cover the affected route, not only the homepage.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2018-25394 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-45617CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: Kados R10 GreenBee SQL Injection via update_release.phpCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.