dbcve.org
Meac300 Fnade4 FirmwareOperating system · Endress

CVE-2025-27455

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-03
Fix available
A fix is available. Upgrade to after 0.16.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The web application is vulnerable to clickjacking attacks. The site can be embedded into another frame, allowing an attacker to trick a user into clicking on something different from what the user perceives, thus potentially revealing confidential information or allowing others to take control of their computer while clicking on seemingly innocuous objects.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The application lacks proper X-Frame-Options or CSP frame-ancestors headers, allowing it to be embedded in iframes on malicious sites. Attackers can overlay invisible UI elements to hijack user clicks, potentially exposing sensitive data or executing unauthorized actions.

MitigationImplement X-Frame-Options: DENY or SAMEORIGIN header, or configure CSP frame-ancestors directive to restrict framing to trusted origins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Meac300 Fnade4 FirmwareOperating system
Affected:<= 0.16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Endress Meac300 Fnade4 device on your network
    Locate the device by checking network inventory, device documentation, or accessing the device management interface to confirm the model and firmware version.
    Affected if The device model matches Endress Meac300 Fnade4 with firmware version 0.16.0 or lower.
  2. Determine the installed firmware version
    Access the device web interface or administrative console and navigate to the system information or firmware version section. Alternatively, check the device startup logs or use the vendor-provided diagnostic tool to query the firmware version.
    Affected if The firmware version is 0.16.0 or any version lower than 0.16.0.
  3. Inspect HTTP response headers for X-Frame-Options
    Use a browser developer tool, curl, or a header inspection tool to capture HTTP responses from the device web interface. Look for the X-Frame-Options header in any response.
    Affected if The X-Frame-Options header is absent from all HTTP responses, or present but set to a weak value like ALLOW-FROM.
  4. Inspect HTTP response headers for CSP frame-ancestors
    Examine the Content-Security-Policy header in HTTP responses from the device. Specifically check if the frame-ancestors directive is configured.
    Affected if The CSP frame-ancestors directive is missing or not configured to restrict framing.
  5. Test if the application can be embedded in an iframe
    Create a test HTML page with an iframe pointing to the device web interface URL. Load the page in a browser and verify whether the content renders successfully within the iframe.
    Affected if The device interface loads successfully inside the iframe, confirming it can be framed by any origin.

You are affected if the Endress Meac300 Fnade4 firmware is version 0.16.0 or lower AND the X-Frame-Options and CSP frame-ancestors headers are missing or not properly configured, allowing the interface to be embedded in iframes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.16.0
Interim mitigation

Implement X-Frame-Options: DENY or SAMEORIGIN header, or configure CSP frame-ancestors directive to restrict framing to trusted origins.

Fix this in Meac300 Fnade4 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27455 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data