PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-89247 WWBN CVE debrief

A remote attacker can inject arbitrary XML into WWBN AVideo's VMAP attributes when the AD_Server plugin is enabled, allowing for ad injection and cross-origin requests from the victim's playback session. This XML injection vulnerability in the plugin/AD_Server/VMAP.php script is reachable without authentication. An attacker can craft a malicious vmaps value containing a non-empty VAST.campaing entry to inject arbitrary <vmap:AdBreak> and <vmap:AdTagURI>/AdSource nodes into the generated XML, resulting in ad injection and cross-origin requests from the victim's playback session. The issue was unfixed at the time of reporting.

Vendor
WWBN
Product
AVideo
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-09-11
Advisory published
2026-09-11
Advisory updated
2026-09-11

Who should care

Defenders responsible for securing WWBN AVideo installations, particularly those using the AD_Server plugin, should assess their exposure and take necessary actions to prevent exploitation.

Why it matters

The XML injection vulnerability in WWBN AVideo's AD_Server plugin allows for ad injection and cross-origin requests, potentially impacting user experience and trust. Defenders should prioritize verifying the plugin configuration, ensuring proper encoding of user-supplied data, and monitoring for suspicious ad requests.

  • Ad injection and cross-origin requests from the victim's playback session.
  • Potential for malicious ad content to be displayed to users.
  • Possible impact on user experience and trust.
  • Need for verification of AD_Server plugin configuration and user-supplied data encoding.

Technical summary

The WWBN AVideo application contains an XML injection vulnerability in the plugin/AD_Server/VMAP.php script. This script is reachable without authentication when the AD_Server plugin is enabled. An attacker can craft a malicious vmaps value containing a non-empty VAST.campaing entry, which can be used to inject arbitrary <vmap:AdBreak> and <vmap:AdTagURI>/AdSource nodes into the generated XML. This can result in ad injection and cross-origin requests from the victim's playback session.

Defensive priority

Defenders should prioritize verifying the AD_Server plugin configuration, ensuring proper encoding of user-supplied data, and monitoring for suspicious ad requests.

Recommended defensive actions

  • Verify the AD_Server plugin configuration to ensure it is properly secured.
  • Ensure proper encoding of user-supplied data in VMAP attributes.
  • Monitor for suspicious ad requests and implement additional security measures as needed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source references indicate an XML injection vulnerability in WWBN AVideo's plugin/AD_Server/VMAP.php. The issue is reachable without authentication when the AD_Server plugin is enabled.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-89247 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-89247 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.