CVE-2023-24610
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 · uneditedNOSH 4a5cfdb allows remote authenticated users to execute PHP arbitrary code via the "practice logo" upload feature. The client-side checks can be bypassed. This may allow attackers to steal Protected Health Information because the product is for health charting.
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 confidenceNOSH allows authenticated users to upload a 'practice logo' but fails to properly validate uploaded files on the server side. Attackers can bypass client-side checks to upload malicious PHP files, which can then be executed by the web server, leading to arbitrary code execution. Since NOSH is a health charting application, this RCE can be leveraged to access Protected Health Information (PHI).
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= 2021-03-13CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm NOSH Chartingsystem versionLocate the version information in the application (typically in an about page, footer, or configuration file). Compare against the affected version 2021-03-13.Affected if The installed version is exactly 2021-03-13.
-
Verify upload functionality existsLocate the 'practice logo' upload feature in the NOSH interface (usually under practice settings or branding configuration). Confirm the feature is accessible to authenticated users.Affected if The practice logo upload feature is present and accessible.
-
Test server-side file validationAttempt to upload a non-image file (such as a .php file or a file with a forged extension) to the upload endpoint. Use a proxy to intercept and modify the request, bypassing any client-side restrictions.Affected if Files with extensions other than images (such as .php, .phtml, .exe) are accepted and stored on the server.
-
Check upload directory accessibilityIdentify the directory where practice logo uploads are stored (common paths include /images, /uploads, or /logos). Attempt to access an uploaded file directly via web browser to see if it is served as a static file or executed as code.Affected if Uploaded files are stored within the web root and can be accessed via URL, enabling potential code execution.
-
Review web server configurationExamine the web server configuration (Apache .htaccess, Nginx config) for the upload directory. Check if script execution is disabled or if the directory allows PHP or other executable file types to run.Affected if The upload directory permits execution of PHP, CGI, or other script types, or lacks restrictions against script execution.
A system is affected if it runs NOSH Chartingsystem version 2021-03-13, has the practice logo upload feature enabled, lacks proper server-side file validation, and stores uploads in a web-accessible directory that permits script execution.
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 strict server-side file type validation using magic bytes/file signatures, store uploads outside the web root or disable script execution in upload directories, and restrict upload functionality to only allow safe image formats.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24610 — 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-24610 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