CVE-2023-48978
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 issue in NCR ITM Web terminal v.4.4.0 and v.4.4.4 allows a remote attacker to execute arbitrary code via a crafted script to the IP camera URL component.
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 confidenceNCR ITM Web terminal versions 4.4.0 and 4.4.4 contain a remote code execution vulnerability in the IP camera URL component. Attackers can inject and execute arbitrary code via a crafted script delivered through this component, likely due to insufficient input validation or sanitization of the URL parameter.
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= 4.4.0= 4.4.4CVSS 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 NCR ITM Web Terminal installationLocate the NCR ITM Web Terminal application on the system and retrieve its version information using the application's built-in version check or system inventory toolsAffected if The installed version is 4.4.0 or 4.4.4
-
Confirm exact version numberVerify the precise version of the installed NCR ITM Web Terminal, as only versions 4.4.0 and 4.4.4 are affectedAffected if The exact version matches 4.4.0 or 4.4.4 exactly
-
Check if IP camera feature is configuredAccess the NCR ITM Web Terminal configuration or administration interface and determine whether the IP camera URL parameter has been configured or enabledAffected if The IP camera URL setting exists and is in use in the environment
-
Inspect IP camera URL parameterExamine the IP camera URL configuration setting within the application for any suspicious or unexpected values that may contain script injection payloadsAffected if The IP camera URL contains unsanitized or unexpected script content
-
Review application logs for injection attemptsSearch application and system logs for entries related to the IP camera URL parameter that may indicate exploitation attempts or anomalous script content in URL fieldsAffected if Logs show requests containing script tags or code in IP camera URL parameters
The environment is affected only if NCR ITM Web Terminal version 4.4.0 or 4.4.4 is installed AND the IP camera URL feature is configured and accessible to an attacker.
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 dataRestrict network access to the IP camera URL component pending a vendor patch. If immediate remediation is required, implement strict input validation and consider deploying a WAF rule to block suspicious URL patterns until the vendor releases an official fix for these specific versions.
- 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-48978 — 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-48978 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