Menu

Star on GitHub · 3.3k

CVE-2026-44960

0.0 · NONE

A stored XSS can be exploited by leveraging the usernames as an attack vector.

Published Jun 23, 2026CWE-79EPSS 0.39%

Overview

CVE-2026-44960 is a none-severity vulnerability. It was published on June 23, 2026 and has a CVSS 3.0 base score of 0.0 (NONE).

This vulnerability has a CVSS 3.0 base score of 0.0, rated NONE. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

A stored XSS can be exploited by leveraging the usernames as an attack vector. When an admin user viewed the audit log details for affected entries, any malicious JavaScript payload embedded in the username would be executed due to missing output sanitisation. Proper escaping has been added to the audit log details output.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-44960?

CVE-2026-44960 is a none-severity vulnerability. It was published on June 23, 2026 and has a CVSS 3.0 base score of 0.0 (NONE).

How severe is CVE-2026-44960?

This vulnerability has a CVSS 3.0 base score of 0.0, rated NONE. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-44960?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-44960?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-44960 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related NONE CVEs from 2026

View all