PatchSiren

PatchSiren cyber security CVE debrief

CVE-2019-25696 Kados CVE debrief

CVE-2019-25696 Kados R10 GreenBee contains an SQL injection vulnerability that allows attackers to manipulate database queries by injecting SQL code through the language_tag parameter. Attackers can submit malicious SQL statements in the language_tag parameter to extract sensitive database information or modify data. The vulnerability has a CVSS score of 8.8 and is classified as HIGH severity. This vulnerability can lead to unauthorized data access, modification, or extraction of sensitive information. Security teams and administrators responsible for Kados R10 GreenBee installations should prioritize patching this vulnerability to prevent potential data breaches and unauthorized access.

Vendor
Kados
Product
Kados R10 GreenBee
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-05
Original CVE updated
2026-07-24
Advisory published
2026-04-05
Advisory updated
2026-07-24

Who should care

Security teams and administrators responsible for Kados R10 GreenBee installations should prioritize patching this vulnerability to prevent potential data breaches and unauthorized access. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Technical summary

The vulnerability exists in the language_tag parameter of Kados R10 GreenBee, allowing attackers to inject malicious SQL code. This can lead to unauthorized data access, modification, or extraction of sensitive information. The CVSS vector for this vulnerability is 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. The source details are limited, and defenders should verify the affected scope and severity with the vendor or other trusted sources.

Defensive priority

High priority should be given to patching this vulnerability due to its high CVSS score and potential impact on data security.

Recommended defensive actions

  • Apply patches or updates provided by the vendor to fix the SQL injection vulnerability
  • Implement input validation and sanitization for user-supplied input
  • Use prepared statements with parameterized queries to prevent SQL injection
  • Monitor database activity for suspicious queries
  • Conduct regular security audits and vulnerability assessments
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-04-05T21:16:48.317Z and was last modified on 2026-07-24T22:10:00.140Z. The NVD entry is currently Analyzed. The source details are limited, and defenders should verify the affected scope and severity with the vendor or other trusted sources. The vulnerability has a CVSS score of 8.8 and is classified as HIGH severity. There is no information on known or unknown affected scope beyond the vendor's advisory.

Sources and references

Verified primary and authoritative sources

  • CVE-2019-25696 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2019-25696

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2019-25696 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2019-25696

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.