CVE
WWBN AVideo 12.4 through 29.7.1 Path Traversal File Deletion via deleteImage.json.php
Affects AVideo 12.4 through 29.7.1 when the ADs plugin is enabled and a registered user holds the 'Can have custom ads' permission. No verified fixed version is listed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The ADs plugin must be enabled. The attacker must be a registered user whose account has the 'Can have custom ads' permission enabled.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
WWBN AVideo, versions in the affected range, contains a path traversal flaw in the ADs plugin's deleteImage.json.php script. A remote attacker with a low-privilege login, such as a user who has created custom ads, can abuse the unchecked is_regular_user parameter or ../ sequences to delete other users' ads or critical files like videos/configuration.php, which can take the site offline and re-expose the installer.
Read the original description
WWBN AVideo 12.4 through 29.7.1 contains a path traversal vulnerability in the ADs plugin deleteImage.json.php that allows authenticated users with custom ads to delete arbitrary files. Attackers can set the unvalidated is_regular_user parameter to another user's id or ../ sequences to delete other users' ads or files like videos/configuration.php, taking the site offline and re-exposing the installer.
Who should check
Teams running WWBN AVideo 12.4 through 29.7.1 with the ADs plugin enabled and users granted custom ads rights
Read the source excerpt
“WWBN AVideo 12.4 through 29.7.1 contains a path traversal vulnerability in the ADs plugin”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The ADs plugin must be enabled. The attacker must be a registered user whose account has the 'Can have custom ads' permission enabled.Apply the patch listed under Evidence.
Workaround: Disable the ADs plugin or revoke the custom ads permission from untrusted users until a verified fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126804 (WWBN AVideo 12.4 through 29.7.1 Path Traversal File Deletion via deleteImage.json.php), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126804 (entry last updated 2026-11-11):
Affected:
- WWBN AVideo: from 12.4, through 29.7.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The ADs plugin must be enabled. (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-58h3-9722-fgpm)
- The attacker must be a registered user whose account has the 'Can have custom ads' permission enabled. (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-58h3-9722-fgpm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Disable the ADs plugin or revoke the custom ads permission from untrusted users until a verified fix is available. (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-58h3-9722-fgpm)
CISA KEV: CVE-2026-126804 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126804 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/WWBN/AVideo/security/advisories/GHSA-58h3-9722-fgpm
- https://github.com/WWBN/AVideo/commit/c2b99663d6442e2182a0f3ab95ea6731a193b301
- https://github.com/WWBN/AVideo/blob/v29.7.1/plugin/ADs/deleteImage.json.php#L53-L63
- https://github.com/WWBN/AVideo/blob/v29.7.1/plugin/ADs/ADs.php#L194-L219
- https://www.vulncheck.com/advisories/wwbn-avideo-12.4-through-29.7.1-path-traversal-file-deletion-via-deleteimage-json-php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126804
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126804"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- WWBN AVideo
From 12.4 · through 29.7.1
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126804
Is CVE-2026-126804 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A registered user with low privileges can use a path traversal flaw in deleteImage.json.php to delete other users' ads, the site-wide ads, and any web-server-writable file outside the ADs directory. Deleting files such as videos/configuration.php can take the site offline and re-expose the installer.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-126804?
AVideo: from 12.4 through 29.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions 12.4 through 29.7.1 of WWBN AVideo are in the affected range. The setup also requires the ADs plugin to be enabled and an account with the 'Can have custom ads' permission. To check, look at the plugin list in the admin panel for ADs and at the user permission settings for that permission.Source: github.com, vulncheck.com
How do I fix CVE-2026-126804?
No fixed version is listed in the checked facts, so no upgrade target can be given. Until a verified fix is available, disable the ADs plugin or revoke the custom ads permission from untrusted users.Source: github.com, vulncheck.com