CVE-2026-19354: lock-upme OPMS · Injection
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:XExploitation evidence
Disclosed: evidence found.
CVE published 9 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| lock-upmeOPMS | Affected
| Fixed in– |
AI-suggested
Until a fix is available, consider restricting access to the vulnerable component or applying application-layer protections such as input validation or web application firewalls targeting SQL injection patterns.
Description
A SQL injection vulnerability exists in the lock-upme OPMS product in the IN Clause Handler component within the file controllers/messages/message.go. The vulnerability arises from manipulation of the argument 'ids' and can be exploited remotely. The product uses a rolling release strategy, so specific affected or fixed versions are not provided. The vendor has not responded to disclosure attempts. The CVSS 3.1 base score is 6.3, indicating a medium severity issue.