PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-40925 WWBN CVE debrief

A vulnerability in WWBN AVideo versions 29.0 and prior allows an attacker to modify site settings, including encoder URL, SMTP credentials, and HTML content, via a cross-origin POST request. This is due to the `objects/configurationUpdate.json.php` endpoint not verifying the request origin or a global token, despite handling sensitive configuration updates.

Vendor
WWBN
Product
AVideo
CVSS
HIGH 8.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-21
Original CVE updated
2026-10-26
Advisory published
2026-04-21
Advisory updated
2026-10-26

Who should care

Administrators of AVideo installations, security teams responsible for web application security, and operators of AVideo platforms should be aware of this vulnerability and take necessary actions to protect their systems. They should verify their configuration, apply the patch, and restrict access to the configuration update endpoint to prevent unauthorized changes. AVideo users and customers may also be impacted and should review their configurations and

Why it matters

This vulnerability allows an attacker to modify sensitive site settings in AVideo versions 29.0 and prior. Administrators should verify their configuration, apply the patch, and restrict access to the configuration update endpoint to prevent unauthorized changes.

  • Potential unauthorized configuration changes
  • Risk of SMTP credential compromise
  • Possible site defacement via HTML modifications
  • Encoder URL changes could disrupt video processing

Technical summary

The `objects/configurationUpdate.json.php` endpoint in AVideo versions 29.0 and prior does not properly validate requests, allowing an attacker to modify site settings via a cross-origin POST request. This is due to the endpoint not verifying the request origin or a global token, despite handling sensitive configuration updates. The vulnerability allows an attacker to modify sensitive site settings, including encoder URL, SMTP credentials, and HTML content. A patch is available in commit f9492f5e6123dff0292d5bb3164fde7665dc36b4.

Defensive priority

Administrators of AVideo installations should verify their configuration and ensure that the update has been applied to prevent unauthorized changes.

Recommended defensive actions

  • Verify AVideo installation version and apply patch if necessary
  • Review site configuration for unauthorized changes
  • Restrict access to configuration update endpoint
  • 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
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. A patch is available in commit f9492f5. The vulnerability allows an attacker to modify sensitive site settings in AVideo versions 29.0 and prior. Evidence is limited to public sources and may not reflect the full scope or impact. Defenders should verify AVideo installation versions, review site configurations, and apply the patch if necessary.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-40925 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-40925

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-40925 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-40925

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.