Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
ExploitRequest restricted administrative endpoint
-
ExecutionBypass improper permission check
-
ImpactDisclose sensitive administrative data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V8 - Authorization Insufficient permission handling
|
| Exploitation Conditions | Exploitation requires a valid low-privilege authenticated account on the Lobster_pro instance (PR:L) and adjacent-network access (AV:A) to reach the HTTP endpoints; the attacker then interacts with endpoints that should require administrative privileges but whose permission checks are not enforced (CWE-280). Confirmed affected: Lobster_pro 4.12.12-LTS, with other versions prior to 25.1.3 potentially affected. Limiting factors: the attacker must already hold credentials and network adjacency rather than attacking an unauthenticated internet-facing surface, and impact is restricted to confidentiality/information disclosure with no integrity or availability effect. The specific administrative endpoints involved and the precise trigger are not detailed in the available sources. |
| Impact | This is a medium-severity issue (CVSS 4.0 base 5.6) and, weighing all signals together, a moderate real-world priority rather than an emergency. The CVSS 4.0 vector describes adjacent-network access (AV:A), low attack complexity (AC:L), a low-privilege authenticated attacker (PR:L), and confidentiality-only impact on both the vulnerable and a subsequent system (VC:H/SC:H, with VI/VA/SI/SA all N) - consistent with the CWE-280 improper-authorization class and the 'Information Disclosure' tag. The vendor/researcher vector carries the threat metric E:A ('Attacked'), which would imply exploitation activity, but this is NOT corroborated by a CISA KEV listing and no EPSS probability was supplied, so the E:A signal cannot be confirmed and should be treated cautiously - it conflicts with the absence of KEV/EPSS data. The vuln.today decision label is 'this_month', indicating it warrants remediation within the normal patching cycle rather than immediate emergency action. Net assessment: the requirement for a pre-existing authenticated account plus network adjacency, combined with confidentiality-only impact, meaningfully limits real-world risk; this is a genuine broken-access-control flaw worth patching this month, not a high-urgency internet-wide threat. |
| Exploit ScenarioDerived | A low-privilege but authenticated user on a network adjacent to a Lobster_pro instance sends requests directly to endpoints that are supposed to be restricted to administrators. Because Lobster_pro does not properly enforce permission checks, those endpoints respond, exposing administrative data or functionality and disclosing sensitive information. No verified working public exploit code was identified; a researcher advisory (SCHUTZWERK) documents the issue. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Information disclosure in Lobster_pro affects version 4.12.12-LTS and potentially other releases prior to 25.1.3, where improper permission checks let an authenticated low-privilege user on an adjacent network reach HTTP endpoints reserved for administrators. The assessed impact is confidentiality-only, with high disclosure of both the vulnerable component and dependent systems but no integrity or availability effect; the CVSS 4.0 base score is 5.6, and no public exploit was identified at time of analysis. It is a medium-severity, moderate-priority issue (this_month) rather than an emergency.
RemediationAI
Upgrade Lobster_pro to 25.1.3 or later; 4.12.12-LTS is confirmed affected and earlier releases are potentially affected. The SCHUTZWERK advisory at https://www.schutzwerk.com/en/blog/schutzwerk-sa-2025-002/ provides the available detail. No workaround is documented in the supplied sources; because exploitation requires an authenticated low-privilege account plus adjacent-network reachability, limiting adjacent-network access to the Lobster_pro HTTP interface and reviewing low-privilege accounts reduce exposure but do not replace upgrading to 25.1.3 or later.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Lobster_pro is identified in the supplied CPE data as cpe:2.3:a:lobster_data_gmbh:lobster_pro:*:*:*:*:*:*:*:*. The root cause is CWE-280, improper handling of insufficient privileges: administrative endpoints are exposed without enforcing the permission checks that should gate them. An attacker who already holds a valid low-privilege account and has adjacent-network access can therefore interact with those endpoints, although the independent assessment restricts impact to information disclosure. The specific administrative endpoints involved and the precise trigger are not described in the available sources.
Know when Lobster Pro gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:A
Authenticated low-privilege user (PR:L) on an adjacent network reaches admin-only endpoints with no described user interaction; confidentiality-only impact with a scope change as admin functions expose other components' data, hence S:C and I/A:N.
Primary rating from Vendor (SCHUTZWERK).
CVSS VectorVendor: SCHUTZWERK
DescriptionCVE.org
Due to improper permission checks in Lobster_pro, attackers are able to interact with endpoints that should require administrative privileges. This issue affects Lobster_pro version 4.12.12-LTS and potentially other versions prior to 25.1.3.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-109944
GHSA-7fg6-gvjw-377p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB