CVE Enrichment

CVSS
9.8 CRITICAL
EPSS
1.16%
EPSS Percentile
66.22%
CISA KEV
Not listed

Description

SENAITE.CORE is the core framework for the SENAITE laboratory information management system. From 2.0.0 to 2.6.0, the SENAITE.CORE JSON API permits unauthenticated remote code execution through a two-request chain involving missing authorization and unsafe evaluation. The state-changing routes in src/bika/lims/jsonapi/update.py, including update, update_many, remove, doActionFor, doActionFor_many, and getusers, do not enforce the senaite.core: Access JSON API permission before resolving attacker-selected objects. In src/bika/lims/jsonapi/init.py, set_fields_from_request passes raw request values for RecordsField and RecordField instances to eval() before field mutator write-permission checks execute. An anonymous attacker can discover the bika_setup object identifier through @@uuid, send a value such as RejectionReasons to /@@API/update, and execute arbitrary Python in the Zope worker before a later mutation failure rolls back ZODB changes. The same unsafe evaluation pattern is present in src/senaite/core/browser/fields/record.py and src/senaite/core/browser/fields/records.py. Successful exploitation can expose or modify laboratory data, files, and accounts and can disrupt the service.

Technical Details

CVSS Version
3.1
CNA / NVD Source
security-advisories@github.com
Published
26-Aug-2026 23:16
Last Modified
10-Sep-2026 04:09
EPSS Date
2026-10-13
CWE
CWE-95, CWE-862

CVSS Vector

CVSS:3.1 AV:N / AC:L / PR:N / UI:N / S:U / C:H / I:H / A:H

References

Last enrichment sync: 14-Oct-2026 07:12
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE (76)

VIEW MORE

Malware (6)

Threat Actors (8)

Vendors (10)

Products (67)

VIEW MORE

Tools (7)

Industries (1)

Countries (2)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.