Cross-Site Request Forgery (CSRF)
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 17 Nov 2026, 01:42 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
AI-suggested
Until a fix is available, users should implement CSRF protections such as validating request origins, using anti-CSRF tokens, or restricting access to the vulnerable endpoint. Monitor vendor communications for updates.
Description
Magewell Pro Convert v1.2.213 contains a Cross-Site Request Forgery (CSRF) vulnerability in the /usapi?method=add-user component. This flaw allows attackers to create user accounts arbitrarily by sending a crafted GET request. The vulnerability has a CVSS score of 6.5, indicating a medium severity impact primarily affecting integrity without compromising confidentiality or availability.