Menu

Star on GitHub · 3.2k

CVE-2026-2932

2.4 · LOW

A security flaw has been discovered in YiFang CMS up to 2.0.5.

Published Feb 22, 2026CWE-79EPSS 0.38%

Overview

CVE-2026-2932 is a low-severity vulnerability. It was published on February 22, 2026 and has a CVSS 3.1 base score of 2.4 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.4, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

A security flaw has been discovered in YiFang CMS up to 2.0.5. The impacted element is the function update of the file app/db/admin/D_adPosition.php of the component Extended Management Module. Performing a manipulation of the argument name/index results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks.

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-2932?

CVE-2026-2932 is a low-severity vulnerability. It was published on February 22, 2026 and has a CVSS 3.1 base score of 2.4 (LOW).

How severe is CVE-2026-2932?

This vulnerability has a CVSS 3.1 base score of 2.4, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

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

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-2932?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-2932 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 LOW CVEs from 2026

View all