Security readout for executives and security teams
Plain-English summary
Kados R10 GreenBee has a high-severity SQL injection flaw in the id_to_modify parameter. An unauthenticated network attacker could potentially read sensitive database data or alter records. This matters most if the product is internet-facing or stores operational, customer, or internal business data.
Executive priority
Prioritize this if Kados R10 GreenBee is in use, especially on externally reachable systems. The risk is high because exploitation requires no login and could expose or change database records. If not deployed, document non-exposure and monitor vendor advisories.
Technical view
CVE-2019-25692 is a CWE-89 SQL injection in Kados R10 GreenBee. The CVSS 4.0 score is 8.8, with network attack vector, low complexity, no privileges, and no user interaction. The provided description states crafted requests to id_to_modify can manipulate database queries to extract or modify data.
Likely exposure
Exposure is limited to organizations running Kados R10 GreenBee, especially if its web interface is reachable from untrusted networks. The sources do not identify specific patched versions, deployment defaults, or affected CPEs.
Exploitation context
A public ExploitDB reference exists, indicating exploit information is publicly available. The source bundle does not show CISA KEV listing or active exploitation evidence, so active exploitation should not be assumed from these sources alone.
Researcher notes
The record cites Kados R10 GreenBee only, with no CPEs and no named fixed version in the provided sources. ExploitDB is referenced, but KEV is false. Treat patch status and active exploitation as unconfirmed unless additional vendor or threat-intelligence sources confirm them.
Mitigation direction
- Check Kados or project guidance for any fixed release or official remediation.
- Remove Kados R10 GreenBee from direct internet exposure where possible.
- Restrict access to trusted networks or VPN users only.
- Apply input validation and parameterized queries if maintaining the application code.
- Monitor database and web logs for suspicious id_to_modify activity.
Validation and detection
- Inventory systems for Kados R10 GreenBee deployments.
- Confirm whether any instance is reachable from the internet.
- Review application logs for unusual id_to_modify requests.
- Review database audit logs for unexpected reads or data changes.
- Use safe authenticated assessment methods; avoid destructive SQL injection testing.
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-2019-25692 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.
CVSS vector scores
1 official scoreWe 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——Primary CVE scoreVulnerability 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
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46505CVE reference · exploit
- Official Product HomepageCVE reference · product
- Product ReferenceCVE reference · product
- VulnCheck Advisory: Kados R10 GreenBee SQL Injection via id_to_modify ParameterCVE reference · 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.