CVE-2018-25075
A public proof of concept exists; no exploitation attested.
- Published2023-01-15
- Fixed in1.4
- WeaknessCWE-89
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability classified as critical has been found in karsany OBridge up to 1.3. Affected is the function getAllStandaloneProcedureAndFunction of the file obridge-main/src/main/java/org/obridge/dao/ProcedureDao.java. The manipulation leads to sql injection. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 1.4 is able to address this issue. The name of the patch is 52eca4ad05f3c292aed3178b2f58977686ffa376. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218376.
Timeline
dates in UTC- 2023-01-1520:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.4 | < 1.4 | 1.4 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As VulDB, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- karsany OBridgeAffected
- = 1.0no fix stated
- = 1.1no fix stated
- = 1.2no fix stated
- = 1.3no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-10-20
Fix
- Update Obridge project obridge to 1.4
Advisories and patches
- github.comPatch
- github.comRelease Notes
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-01epicosy/obridge
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionnone2024-11-25
- CNACVSS 3.14.6known since 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNACVSS 2.04known since 2026-10-23
- CNAweakness (CWE)CWE-89known since 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- PoC-in-GitHubproof of concept1known since 2026-11-01
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2018-13834same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-pjx3-rq8r-cfr8same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-01-15
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-pjx3-rq8r-cfr8
Frequently asked questions
What is CVE-2018-25075?
Is CVE-2018-25075 actively exploited?
What is the CVSS score for CVE-2018-25075?
Running karsany OBridge? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-pjx3-rq8r-cfr8
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0