dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2025-22493

MEDIUM · 5.6 CVSS v3.1 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Zero-click

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
Secure flag not set and SameSIte was set to Lax in the Foreseer Reporting Software (FRS). Absence of this secure flag could lead into the session cookie being transmitted over unencrypted HTTP connections. This security issue has been resolved in the latest version of FRS v1.5.100.

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 Foreseer Reporting Software (FRS) session cookie is missing the Secure flag, allowing transmission over unencrypted HTTP connections. Additionally, the SameSite attribute is set to 'Lax' instead of a stricter value, which could enable the cookie to be sent in certain cross-site request scenarios, potentially leading to session hijacking.

MitigationUpgrade to FRS v1.5.100 or later where the Secure flag is properly set on the session cookie and SameSite is configured appropriately. If immediate patching is not possible, configure the web server or application to add Secure=true and SameSite=Strict to session cookies.

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

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

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 Foreseer Reporting Software version
    Locate the FRS installation directory and check the version file, or use the software's built-in 'About' or version check command. Common locations include the installation folder or the application's admin interface.
    Affected if Version is below 1.5.100 (the patched release)
  2. Capture the session cookie from FRS
    Log into the FRS application and use browser developer tools (Application/Storage tab) or a proxy tool to capture the session cookie. Note the cookie name and its attributes.
    Affected if A session cookie exists and is being set by the FRS application.
  3. Inspect the Secure flag on the session cookie
    Examine the cookie details in browser dev tools or proxy output. Look for the 'Secure' attribute in the Set-Cookie header or cookie properties.
    Affected if The Secure flag is absent or not set to true on the session cookie.
  4. Inspect the SameSite attribute on the session cookie
    Examine the SameSite value in the cookie properties or Set-Cookie header.
    Affected if SameSite is set to 'Lax' or is missing/undefined instead of 'Strict'.
  5. Verify if HTTP access is enabled
    Check the FRS web server configuration or application settings to determine if unencrypted HTTP connections on port 80 are permitted.
    Affected if HTTP access is enabled, making the missing Secure flag exploitable for session hijacking over unencrypted connections.

The environment is affected if FRS version is below 1.5.100 and the session cookie lacks the Secure flag or has SameSite set to Lax, especially if HTTP access is enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FRS v1.5.100 or later where the Secure flag is properly set on the session cookie and SameSite is configured appropriately. If immediate patching is not possible, configure the web server or application to add Secure=true and SameSite=Strict to session cookies.

Recommended fix Moderate confidence

FRS v1.5.100

  1. Obtain Foreseer Reporting Software v1.5.100 from official Eaton sources
  2. Backup the current FRS configuration and database
  3. Deploy FRS v1.5.100 following standard upgrade procedures
  4. Verify the Secure flag is now set on session cookies and SameSite attribute is configured appropriately
  5. Confirm HTTPS is enforced for all authentication and session traffic

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22493 — 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-22493 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