CVE-2026-18765: SQL Injection in Teracity Sotware's Teracity E-OSB Platform
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Teracity Software Technologies Inc. E-OSB allows SQL Injection.
This issue affects E-OSB: before V02.26.07.08.01.
Security readout for executives and security teams
Plain-English summary
Teracity E-OSB versions before V02.26.07.08.01 contain a critical SQL injection vulnerability. A network attacker may be able to access, alter, or disrupt backend data without authentication or user interaction. The public sources do not identify affected endpoints or confirm attacks in the wild.
Executive priority
Prioritize immediate ownership, exposure assessment, and an expedited upgrade. Internet-accessible or business-critical deployments warrant emergency handling because the vulnerability requires no stated authentication and could affect sensitive data and service availability. Absence from KEV does not reduce the technical severity.
Technical view
CVE-2026-18765 is a CWE-89 SQL injection flaw in Teracity Software Technologies E-OSB before V02.26.07.08.01. Its CVSS 3.1 score is 9.8, with network reachability, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running E-OSB versions earlier than V02.26.07.08.01. Risk is greatest where affected interfaces are reachable from untrusted networks. The supplied records contain no CPEs, endpoint details, deployment prevalence, or reliable product-discovery indicators.
Exploitation context
The supplied record is not listed in CISA KEV, and no cited source confirms active exploitation or public exploit availability. The CVSS vector indicates potentially remote, unauthenticated exploitation, but public technical details are insufficient to assess exploit reliability, affected parameters, or detection signatures.
Researcher notes
The public record establishes the affected version boundary, CWE-89 classification, and CVSS vector, but provides no vulnerable endpoint, parameter, database context, root cause, indicators, or exploit evidence. The structured affected-product entry is sparse and contains no CPE mapping; validate asset identification directly with product owners and Teracity guidance.
Mitigation direction
Upgrade affected E-OSB deployments to V02.26.07.08.01 or later after confirming the supported release with Teracity.
Until upgraded, restrict E-OSB access to trusted networks and authorized users.
Apply any compensating controls published by Teracity or the cited government advisory.
Monitor application, database, and perimeter logs for unusual requests, SQL errors, or unexpected database activity.
Validation and detection
Inventory all E-OSB deployments and record their exact installed versions.
Treat every deployment earlier than V02.26.07.08.01 as affected.
Identify affected interfaces reachable from internet-facing or otherwise untrusted networks.
Confirm the upgraded version after maintenance and test normal business transactions.
Review relevant logs around and after September 1, 2026 for anomalies requiring investigation.
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.
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.
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
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
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.
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
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.