Security readout for executives and security teams
Plain-English summary
Nayshlok Voyager has a SQL injection flaw in DatabaseAccess.java. Public sources say it can affect confidentiality, integrity, and availability, but require adjacent-network access and low privileges. A patch commit is identified; affected versions are not clearly documented.
Executive priority
Treat as a moderate priority unless Voyager protects sensitive data or is reachable from less-trusted adjacent networks. The main business risk is unauthorized database access or modification in affected deployments.
Technical view
CVE-2014-125074 is CWE-89 in Nayshlok Voyager, tied to Voyager/src/models/DatabaseAccess.java. CVSS v3.1 is 5.5 with adjacent attack vector, low attack complexity, low privileges, and no user interaction. Sources identify patch commit f1249f438cd8c39e7ef2f6c8f2ab76b239a02fae.
Likely exposure
Exposure appears limited to organizations running Nayshlok Voyager or derived code containing the affected DatabaseAccess.java logic. Versions and CPEs are not provided, so inventory must confirm code presence directly.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates exploitation requires adjacent access and a low-privileged context.
Researcher notes
Evidence is sparse: functionality, affected versions, and product lifecycle status are not specified. Analysis should focus on code comparison against the named patch and confirming whether the vulnerable file exists in deployed Voyager variants.
Mitigation direction
- Apply or verify the patch commit f1249f438cd8c39e7ef2f6c8f2ab76b239a02fae.
- Check vendor or project guidance for any release-specific remediation notes.
- Inventory deployed Voyager instances and forks for the affected DatabaseAccess.java file.
- Prioritize remediation where Voyager can reach sensitive databases.
Validation and detection
- Confirm the deployed code includes patch commit f1249f438cd8c39e7ef2f6c8f2ab76b239a02fae.
- Review Voyager/src/models/DatabaseAccess.java for remaining unsafe SQL construction.
- Confirm whether any production systems run Nayshlok Voyager or forks.
- Check application and database logs for unusual query errors or unauthorized data changes.
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-2014-125074 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.218005CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.218005CVE reference · signature, permissions-required
- https://github.com/Nayshlok/Voyager/commit/f1249f438cd8c39e7ef2f6c8f2ab76b239a02faeCVE reference · patch
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.