CVE-2023-38257
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 · uneditedIagona ScrutisWeb versions 2.1.37 and prior are vulnerable to an insecure direct object reference vulnerability that could allow an unauthenticated user to view profile information, including user login names and encrypted passwords.
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 confidenceIagona ScrutisWeb versions 2.1.37 and prior contains an Insecure Direct Object Reference (IDOR) vulnerability in its profile viewing functionality. The application fails to enforce proper authorization checks on profile endpoints, allowing unauthenticated attackers to directly reference user profile resources by manipulating object identifiers. This exposes sensitive user credentials including login names and encrypted passwords to unauthorized parties.
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<= 2.1.37CVSS 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.
-
Confirm Iagona ScrutisWeb installationIdentify whether the Iagona ScrutisWeb application is deployed in your environment. Check for web server responses, application directories, or service listings that indicate ScrutisWeb is running.Affected if ScrutisWeb is present in the environment
-
Check installed version against affected rangeLocate the installed version of ScrutisWeb. This is typically found in application metadata, about pages, configuration files, or by querying the application directly. Compare your version to the affected range: versions 2.1.37 and prior.Affected if The installed version is 2.1.37 or lower
-
Identify profile endpoint accessibilityLocate the profile viewing functionality in the web application. Common paths include /profile, /user/profile, /profile/view, or similar endpoints that display user information. Determine if these endpoints are accessible without authentication.Affected if Profile endpoints are accessible without requiring authentication
-
Test for IDOR via object identifier manipulationAttempt to access profile resources by directly manipulating object identifiers in the URL or request parameters. For example, if viewing your own profile at /profile/view?id=1, try incrementing the id value to access different user profiles without authentication.Affected if Manipulating profile identifiers allows access to other user profiles without authorization
You are affected if ScrutisWeb version 2.1.37 or lower is installed AND the profile viewing endpoints are accessible without authentication AND arbitrary profile access is possible via IDOR.
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 object-level authorization checks to verify the requesting user has permission to access the requested profile resource, and consider requiring authentication for all profile access endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38257 — 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-38257 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