CVE-2026-72747 WWBN CVE debrief

Who should care

Administrators and developers of AVideo should assess exposure and prioritize remediation to prevent potential XSS attacks. They should verify and sanitize user input, especially phone fields, during registration to prevent potential XSS attacks. Additionally, they should review and update administrators' management pages to ensure proper rendering and sanitization of user-provided data. AVideo's users and administrators are at risk of XSS attacks due to a

Why it matters

The CVE-2026-72747 vulnerability in AVideo allows unauthenticated attackers to inject malicious JavaScript, which can be executed in administrators' browser sessions. Defenders should prioritize verifying and sanitizing user input, especially phone fields, during registration to prevent potential XSS attacks.

• Defenders should verify and sanitize user input to prevent potential XSS attacks.
• Administrators' management pages may be vulnerable to XSS attacks if not properly sanitized.
• The vulnerability has a CVSS score of 5.1 and MEDIUM severity, indicating a moderate risk.

Technical summary

AVideo fails to sanitize the phone field during user registration, allowing unauthenticated attackers to inject malicious JavaScript that persists in the database. When administrators visit the users management page, the unsanitized phone value is rendered via innerHTML, executing the injected script in the admin's browser session. The vulnerability has a CVSS score of 5.1 and MEDIUM severity, indicating a moderate risk. Defenders should prioritize verifying and sanitizing user input, especially phone fields, during registration to prevent potential XSS attacks. AVideo's failure to sanitize user input allows attackers to inject malicious scripts, which can be executed in administrators' browser sessions.

Defensive priority

Administrators should prioritize verifying and sanitizing user input, especially phone fields, during registration to prevent potential XSS attacks.

Recommended defensive actions

• Verify and sanitize user input, especially phone fields, during registration to prevent potential XSS attacks.
• Review and update administrators' management pages to ensure proper rendering and sanitization of user-provided data.
• Consider implementing additional security measures, such as Content Security Policy (CSP), to mitigate XSS attacks.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 5.1 and MEDIUM severity. AVideo fails to sanitize the phone field during user registration, allowing unauthenticated attackers to inject malicious JavaScript.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.