LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25690: Kados R10 GreenBee SQL Injection via mng_profile_id

Kados R10 GreenBee contains an SQL injection vulnerability that allows attackers to manipulate database queries by injecting SQL code through the mng_profile_id parameter. Attackers can send crafted requests with malicious SQL payloads in the mng_profile_id parameter to extract sensitive database information.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Kados R10 GreenBee has a high-severity SQL injection issue in the mng_profile_id parameter. An unauthenticated remote attacker may be able to manipulate database queries and extract sensitive information. A public ExploitDB entry exists, but the provided sources do not show confirmed active exploitation or CISA KEV listing.

Executive priority

Prioritize this for rapid assessment and remediation if Kados R10 GreenBee is present, especially on internet-facing systems. The issue can expose sensitive database information without authentication. If the product is not deployed, business risk is negligible after inventory confirmation.

Technical view

CVE-2019-25690 is CWE-89 SQL injection affecting Kados R10 GreenBee. The CVSS 4.0 score is 8.8 with network attack vector, low complexity, no privileges, and no user interaction. The primary confidentiality impact is high, with limited integrity impact and no availability impact indicated in the provided CVSS vector.

Likely exposure

Exposure is most relevant where Kados R10 GreenBee is deployed and reachable over a network, especially if internet-facing. The source bundle does not identify affected subversions beyond R10 GreenBee or provide CPE data, so asset discovery may require product-specific inventory checks.

Exploitation context

A public ExploitDB reference is cited, indicating exploit information is publicly available. However, the source bundle states KEV is false and does not provide evidence of active exploitation in the wild. Treat internet-exposed deployments as urgent because exploitation requires no privileges or user interaction.

Researcher notes

The evidence identifies the vulnerable parameter and product but does not include patch status, fixed versions, or proof of active exploitation. Avoid assuming broader Kados product impact. Focus validation on asset presence, network exposure, logs, and vendor advisory changes.

Mitigation direction

  • Check Kados or VulnCheck guidance for vendor-confirmed fixes or updates.
  • Remove Kados R10 GreenBee from direct internet exposure where possible.
  • Restrict access to trusted networks or authenticated administrative paths.
  • Apply compensating controls to block suspicious SQL injection patterns.
  • Back up relevant databases before making remediation changes.
  • Monitor application and database logs for unusual mng_profile_id activity.

Validation and detection

  • Inventory systems for Kados R10 GreenBee deployments.
  • Confirm whether any deployment is internet-facing or broadly reachable.
  • Review vendor and advisory pages for updated affected-version details.
  • Check application logs for anomalous requests involving mng_profile_id.
  • Verify access controls limit untrusted network access.
  • Document remediation status and compensating controls for each instance.
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-25690 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-25690Attack 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.