CVE-2025-34114: Laser Romae s.r.l OpenBlow · Exposed Dangerous Method or Function
Affects Laser Romae s.r.l OpenBlowSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Laser Romae s.r.l. OpenBlow | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-34114, European organizations should implement the following specific measures: 1) Configure the OpenBlow platform to include robust HTTP security headers in all responses, specifically: Content-Security-Policy with strict directives to block inline scripts and restrict resource origins; Referrer-Policy to limit referer information leakage; Permissions-Policy to control access to powerful browser features; Cross-Origin-Embedder-Policy and Cross-Origin-Resource-Policy to prevent unauthorized cross-origin resource loading. 2) Avoid relying on HTML <meta> tags for CSP enforcement, as modern browsers prioritize header-based policies. 3) Conduct thorough security reviews of OpenBlow deployments to ensure no dangerous methods or functions are exposed without proper access controls, aligning with CWE-749 and CWE-94 mitigations. 4) Limit administrative and privileged user access to trusted personnel and enforce strong authentication and monitoring to reduce risk of insider exploitation. 5) Regularly update and patch OpenBlow as vendor updates become available, and monitor security advisories for new developments. 6) Employ web application firewalls (WAFs) with rules targeting XSS and clickjacking attempts as an additional layer of defense. 7) Educate users and administrators about phishing and social engineering risks that could lead to privilege escalation and exploitation of this vulnerability.
Description
A client-side security misconfiguration vulnerability exists in OpenBlow whistleblowing platform across multiple versions and default deployments, due to the absence of critical HTTP response headers including Content-Security-Policy, Referrer-Policy, Permissions-Policy, Cross-Origin-Embedder-Policy, and Cross-Origin-Resource-Policy. This omission weakens browser-level defenses and exposes users to cross-site scripting (XSS), clickjacking, and referer leakage. Although some instances attempt to enforce CSP via HTML <meta> tags, this method is ineffective, as modern browsers rely on header-based enforcement to reliably block inline scripts and untrusted resources.