dbcve.org
InsightApplication · Floorsightsoftware

CVE-2023-45892

HIGH · 7.5 CVSS v3.1 Published 2024-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue discovered in the Order and Invoice pages in Floorsight Insights Q3 2023 allows an unauthenticated remote attacker to view sensitive customer information.

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 · moderate confidence

The vulnerability allows unauthenticated remote attackers to access Order and Invoice pages in Floorsight Insights Q3 2023, bypassing authentication requirements and exposing sensitive customer information such as names, addresses, and purchase details.

MitigationImplement proper authentication and session validation on Order and Invoice pages, and add role-based authorization checks to ensure only authenticated users with appropriate permissions can access customer data.

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
InsightApplication
Affected:<= q3_2023

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Floorsightsoftware Insight installation
    Locate the Floorsight Insights application in your environment. Check for directories or services running 'Floorsight', 'Insights', or related naming conventions. Look for web application endpoints that serve Q3 2023 content.
    Affected if Floorsight Insights Q3 2023 or earlier is installed and running
  2. Determine the installed version
    Query the application for its version number, typically found in the software itself, an about page, configuration files, or the application banner/header. Compare your version against the affected range: any version <= q3_2023.
    Affected if The installed version is q3_2023 or any earlier version
  3. Verify Order page accessibility without authentication
    Attempt to access the Order page endpoint (commonly /order, /orders, /invoice/orders, or similar paths) using a web browser or HTTP client WITHOUT providing any login credentials. Check if the page loads and displays order data.
    Affected if The Order page loads and displays order information without requiring authentication
  4. Verify Invoice page accessibility without authentication
    Attempt to access the Invoice page endpoint (commonly /invoice, /invoices, /billing, or similar paths) using a web browser or HTTP client WITHOUT providing any login credentials. Check if the page loads and displays invoice data.
    Affected if The Invoice page loads and displays customer invoice information without requiring authentication
  5. Confirm sensitive customer data exposure
    On any Order or Invoice page accessed without authentication, verify whether sensitive information such as customer names, physical addresses, purchase details, or payment information is visible in the response.
    Affected if Customer PII (names, addresses, purchase details) is visible on Order or Invoice pages without authentication

You are affected if Floorsight Insights version q3_2023 or earlier is running and the Order or Invoice pages are accessible without any authentication credentials, exposing customer data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and session validation on Order and Invoice pages, and add role-based authorization checks to ensure only authenticated users with appropriate permissions can access customer data.

Fix this in Insight Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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