LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25700: Kados R10 GreenBee SQL Injection via sort_direction Parameter

Kados R10 GreenBee contains an SQL injection vulnerability that allows attackers to manipulate database queries by injecting SQL code through the sort_direction parameter. Attackers can submit malicious SQL statements in the sort_direction parameter to extract sensitive database information or modify data.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Kados R10 GreenBee has a SQL injection flaw in the sort_direction parameter. An unauthenticated remote attacker may be able to read sensitive database information or alter data. Public exploit information is referenced, but CISA KEV is not listed in the provided sources. Treat exposed instances as high priority.

Executive priority

Prioritize this if Kados R10 GreenBee is deployed, especially on public-facing systems. The issue can affect sensitive database data and has public exploit reference material. If the product is not used, business risk is likely negligible after inventory confirmation.

Technical view

CVE-2019-25700 is a CWE-89 SQL injection in Kados R10 GreenBee via sort_direction. The CVSS 4.0 score is 8.8, with network attack vector, low complexity, no privileges, and no user interaction. Sources cite potential database confidentiality impact and limited integrity impact. No vendor patch details are provided in the source bundle.

Likely exposure

Risk is highest for internet-accessible Kados R10 GreenBee deployments, especially if unauthenticated users can reach affected application views using sort_direction. Internal-only systems remain at risk from insider access or compromised network footholds. The sources do not identify affected versions beyond R10 GreenBee.

Exploitation context

ExploitDB is listed as a public exploit reference, indicating exploit details are publicly available. The provided data does not show CISA KEV listing or confirmed active exploitation. Attackers would likely target exposed web application endpoints to access or manipulate backend database content.

Researcher notes

The record names only Kados R10 GreenBee and the sort_direction parameter. No patch, fixed version, or vendor workaround is included in the provided sources. Avoid assuming broader Kados versions are affected. Public exploit availability increases validation urgency, but active exploitation is not evidenced here.

Mitigation direction

  • Identify any Kados R10 GreenBee deployments and owners.
  • Restrict internet access to affected Kados interfaces where possible.
  • Check Kados, VulnCheck, and CVE sources for vendor remediation guidance.
  • Apply any vendor-provided update or workaround when available.
  • Review database permissions to limit application account impact.
  • Increase logging and monitoring for suspicious sort_direction requests.

Validation and detection

  • Inventory assets for Kados R10 GreenBee usage.
  • Confirm whether exposed application routes accept sort_direction from unauthenticated users.
  • Review web logs for unusual sort_direction values.
  • Check whether WAF or application controls block SQL injection patterns.
  • Verify database activity for unexpected reads or modifications.
  • Document current product version and remediation status.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2019-25700 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2019-25700Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KadosKados R10 GreenBeeR10 GreenBeeListed
Weakness

CWE details

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.