LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46355: OCS Inventory 2.9.1 is affected by Cross Site Scripting (XSS).

OCS Inventory 2.9.1 is affected by Cross Site Scripting (XSS). To exploit the vulnerability, the attacker needs to manipulate the name of some device on your computer, such as a printer, replacing the device name with some malicious code that allows the execution of Stored Cross-site Scripting (XSS).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OCS Inventory 2.9.1 can store unsafe device names and later show them in the web console. If a device name contains malicious script, it may run in a user’s browser when viewed. This could expose sessions or data visible to that user.

Executive priority

Treat this as a targeted remediation item, not an emergency based on current evidence. Prioritize if OCS Inventory 2.9.1 is used for privileged asset management, exposed beyond trusted administrators, or accessed by high-privilege users.

Technical view

CVE-2021-46355 is a stored XSS issue in OCS Inventory 2.9.1. The public description says an attacker manipulates a local device name, such as a printer name, so malicious code is stored and executed when rendered. CVE metadata does not provide CVSS, CWE, CPEs, or patch details.

Likely exposure

Organizations running OCS Inventory 2.9.1 are the only clearly identified exposure. The source bundle does not identify other affected versions, affected CPEs, internet exposure requirements, or whether authentication is required to reach the vulnerable view.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires a manipulated device name that OCS Inventory collects and later displays to a user in the web interface.

Researcher notes

Evidence is sparse. The CVE record and referenced write-up describe stored XSS through device names, but do not provide standardized scoring, affected CPEs, fixed versions, or exploit-in-the-wild confirmation in the provided bundle.

Mitigation direction

  • Identify any OCS Inventory 2.9.1 deployments.
  • Check OCS Inventory vendor guidance for fixed versions or official mitigations.
  • Restrict administrative console access to trusted users and networks.
  • Review collected device names and rename suspicious entries.
  • Ensure output encoding or sanitization is applied where device names are displayed.

Validation and detection

  • Confirm whether OCS Inventory 2.9.1 is deployed.
  • Review asset inventory data for suspicious HTML or script-like device names.
  • Check whether device names render as text in the web interface.
  • Review access logs for unusual changes to device or printer names.
  • Document whether compensating access controls protect the console.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-46355 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.