An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file access feature, allowing access without authentication. This includes device parameter files, enabling an attacker to read and modify application settings, including customer-defined passwords. Additionally, exposure of the custom application directory may allow execution of arbitrary Lua code within the sandboxed AppEngine environment.
Security readout for executives and security teams
Plain-English summary
Affected SICK vision devices expose sensitive filesystem areas through an unauthenticated HTTP file-access feature. A remote attacker could read or alter settings and customer-defined passwords. Access to the custom application directory may also permit arbitrary Lua execution inside the device’s sandboxed AppEngine environment, potentially disrupting industrial operations.
Executive priority
Treat reachable affected devices as an immediate remediation priority because attackers may alter credentials and operational settings without authentication. First isolate exposure, then coordinate vendor-approved remediation and credential rotation. Devices confined to tightly controlled networks remain important but can follow reachable systems after access controls are independently verified.
Technical view
CWE-552 access restrictions improperly expose critical directories through AppEngine Fileaccess over HTTP. Exploitation requires no credentials or user interaction and has low complexity. The vendor-assigned CVSS 3.1 score is 9.4, reflecting high confidentiality and integrity impact, plus limited availability impact. Lua execution is described as sandboxed; broader device compromise is not established.
Likely exposure
InspectorP63x, P64x, and P65x are listed as affected in all versions. InspectorP61x, P62x, and ICR890-4 list version “0,” whose precise meaning is unclear. Risk is greatest where the HTTP file-access feature is reachable from untrusted, enterprise, or internet-connected networks.
Exploitation context
The supplied sources do not report active exploitation, and this CVE is not listed as KEV in the bundle. Nevertheless, network access, low complexity, and absent authentication make exploitation practical if the vulnerable HTTP interface is reachable. No exploit method should be required to prioritize defensive action.
Researcher notes
The evidence supports unauthorized filesystem read/write and sandboxed Lua execution, but does not establish sandbox escape, full operating-system takeover, or active exploitation. The “0” version entries require clarification from SICK. The bundle names no specific fixed release, so patch availability and exact upgrade paths should be confirmed through the canonical advisory.
Mitigation direction
Consult SICK advisory SCA-2026-0010 for product-specific updates or mitigations.
Restrict HTTP file-access reachability to authorized management systems and trusted networks.
Segment affected devices from internet-facing and general enterprise networks.
After containment, rotate customer-defined passwords that may have been exposed.
Back up and verify configurations before applying vendor-recommended remediation.
Validation and detection
Inventory the listed SICK models and record exact firmware versions.
Confirm whether AppEngine Fileaccess over HTTP is enabled and network-reachable.
Review firewall paths for access from internet, enterprise, wireless, and vendor networks.
Compare device parameters and custom application files against trusted baselines.
Review available logs for unexpected HTTP access or configuration changes.
Verify vendor guidance resolves exposure without disrupting required industrial workflows.
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 · low confidence lookup
CWE-552: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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
7Source 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.
ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5SICK AG
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-552 · source CWE mapping
Files or Directories Accessible to External Parties
Files or Directories Accessible to External Parties represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.