Security readout for executives and security teams
Plain-English summary
Kados R10 GreenBee has a SQL injection flaw in the id_project parameter. An unauthenticated network attacker could potentially read sensitive database data or alter some records. The CVSS 4.0 score is 8.8, and a public ExploitDB reference exists, so exposed deployments should be treated as urgent.
Executive priority
High priority for organizations running Kados R10 GreenBee, especially if internet-facing. The main business concern is unauthorized access to sensitive database information and possible data modification. If the product is not present, no action beyond documentation is needed.
Technical view
CVE-2019-25702 is CWE-89 SQL injection affecting Kados R10 GreenBee. The reported vector is network-accessible, low complexity, no privileges, and no user interaction. Reported impact is high confidentiality and low integrity impact, with no availability impact. Sources identify the vulnerable input as id_project.
Likely exposure
Risk is highest where Kados R10 GreenBee is reachable from the internet or untrusted internal networks. Exposure depends on whether the affected R10 GreenBee version is deployed and whether the vulnerable functionality is accessible.
Exploitation context
The source bundle includes an ExploitDB entry, indicating public exploit information exists. CISA KEV status is false in the provided data, and no cited source states active exploitation in the wild.
Researcher notes
Evidence identifies the vulnerable parameter and product but does not include a vendor patch statement in the provided sources. Avoid assuming all Kados versions are affected beyond R10 GreenBee. Public exploit availability raises urgency, but active exploitation is not established here.
Mitigation direction
- Identify any Kados R10 GreenBee deployments and owners.
- Restrict access to trusted networks until vendor guidance is confirmed.
- Check Kados and VulnCheck references for remediation or upgrade guidance.
- Prioritize database backup and integrity review for exposed instances.
- Monitor web and database logs for suspicious id_project parameter activity.
Validation and detection
- Inventory systems for Kados R10 GreenBee.
- Confirm whether affected functionality using id_project is enabled and reachable.
- Review application logs for unusual id_project values or database errors.
- Check database audit logs for unexpected reads or modifications.
- Verify whether any vendor-provided update or workaround has been applied.
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-25702 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_project 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.
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.