VulnerabilityPublished 15 Nov 2023Updated 29 Sep 2025

CVE-2023-48198: A Cross-Site Scripting (XSS)

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 15:59 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, organizations should first monitor for an official patch or update from the Grocy development team and apply it promptly once available. In the interim, administrators should restrict access to the Grocy instance to trusted users only, ideally behind VPNs or internal networks, to reduce exposure. Input validation and output encoding should be enforced on the product description field to prevent script injection; if possible, implement web application firewalls (WAFs) with rules to detect and block XSS payloads targeting the '/api/stock/products' endpoint. Educate users about the risks of clicking on suspicious links or viewing untrusted content within Grocy. Additionally, consider implementing Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the browser context. Regularly audit and sanitize existing product descriptions to remove any malicious or suspicious content. Finally, monitor logs for unusual activity that could indicate exploitation attempts.

Description

A Cross-Site Scripting (XSS) vulnerability in the 'product description' component within '/api/stock/products' of Grocy version <= 4.0.3 allows attackers to obtain a victim's cookies.

Impact

For European organizations using Grocy for inventory or household management, this XSS vulnerability poses a risk primarily to confidentiality and integrity. If exploited, attackers could steal session cookies, leading to account compromise and unauthorized access to potentially sensitive inventory or personal data. While Grocy is often used in small to medium business environments or by individuals, organizations relying on it for operational management could face disruption or data leakage. The impact is heightened in environments where Grocy is integrated with other internal systems or contains sensitive business data. Additionally, compromised accounts could be leveraged for further attacks within an organization's network. The vulnerability could also undermine user trust and compliance with data protection regulations such as GDPR, especially if personal data is exposed or mishandled due to the exploit.

References

Community reviews

Loading reviews…