CVE-2023-45893
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 · uneditedAn indirect Object Reference (IDOR) in the Order and Invoice pages in Floorsight Customer Portal 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 confidenceAn IDOR vulnerability in Floorsight Customer Portal Q3 2023 allows unauthenticated attackers to access sensitive customer data via Order and Invoice pages by manipulating object references (likely order/invoice IDs). The lack of proper authorization validation enables unauthorized access to resources belonging to other customers.
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<= q3_2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Floorsightsoftware Customer Portal installationLocate the Floorsightsoftware Customer Portal application in your environment. Check for web server directories, installed packages, or service listings that contain 'Floorsight' or 'Customer Portal'.Affected if Floorsightsoftware Customer Portal is present in the environment
-
Determine the installed versionCheck the version of the Floorsightsoftware Customer Portal. Look in application metadata, about pages, or configuration files for version information. Compare against q3_2023.Affected if The installed version is q3_2023 or earlier (any version <= q3_2023)
-
Verify Order and Invoice pages are accessibleCheck if the Order and Invoice pages are exposed and functional in the Customer Portal. These are typically found at URLs containing patterns like /order/* or /invoice/*.Affected if Order and Invoice pages are accessible within the application
-
Check for sequential object reference usageInspect the URL patterns used for Order and Invoice pages. Look for sequential numeric IDs (e.g., /order/123, /invoice/456) rather than opaque identifiers like UUIDs.Affected if Sequential numeric IDs are used in URLs to access order or invoice data
-
Test authorization controls on Order and Invoice endpointsAttempt to access Order or Invoice pages with different object reference values (e.g., modify the ID parameter). Verify if the application properly validates that the requesting user owns or has permission to view the requested order/invoice.Affected if The application allows access to order/invoice data by manipulating object references without proper authorization validation
A user is affected if Floorsightsoftware Customer Portal version q3_2023 or earlier is installed and the Order/Invoicing pages use sequential IDs without proper authorization checks on object references.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on Order and Invoice pages to verify the requesting user has legitimate access to the requested data. Additionally, implement indirect object references (e.g., UUIDs) instead of sequential IDs to prevent enumeration attacks.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45893 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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