CVE-2023-35189
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 a remote code execution vulnerability that could allow an unauthenticated user to upload a malicious payload and execute it.
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 confidenceUnauthenticated remote code execution vulnerability in Iagona ScrutisWeb versions 2.1.37 and prior allows attackers to upload malicious payloads directly to the server and execute them without any authentication.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 ScrutisWeb installationLocate the ScrutisWeb application directory or service on the system. Common paths include /opt/scrutisweb, C:\Program Files\ScrutisWeb, or check running services for 'ScrutisWeb' or 'scutis' processes.Affected if ScrutisWeb is installed and running on the system
-
Determine installed versionCheck the web application UI for a version number (typically in an About page, footer, or help menu). Alternatively, examine the application's config files, changelog, or manifest files within the installation directory for a version string.Affected if The installed version is 2.1.37 or lower, or if no version information is found and the application is confirmed to be ScrutisWeb <= 2.1.37
-
Verify network accessibilityDetermine if the ScrutisWeb web interface is accessible over the network. Check firewall rules, reverse proxy configurations, and binding addresses (e.g., 0.0.0.0 vs 127.0.0.1). Attempt to access the login page or public endpoints from an external host if authorized.Affected if The web interface is accessible from untrusted networks without VPN or authentication barriers
-
Check for unauthorized uploaded filesInspect the application's upload directory (commonly /uploads, /files, or within the web root) for unexpected or suspicious file types such as .asp, .php, .jsp, .exe, or script files that were not intentionally placed there by administrators.Affected if Unexpected script files or executables exist in upload directories, indicating possible exploitation
You are affected if ScrutisWeb version 2.1.37 or lower is installed and its web interface is network-accessible, as unauthenticated attackers can directly upload and execute malicious payloads.
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 dataUpdate to a version newer than 2.1.37; if immediate patching is not feasible, restrict network exposure and implement strict input validation and file type restrictions on upload endpoints.
- Consultation4.0 h
- Implementation3.0 h
- Testing8.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 $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35189 — 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-35189 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