CVE-2026-115831: VOD Infomaniak <= 1.5.15 - Missing Authorization to Authenticated (Subscriber+) Unauthorized Video Importation via vodimportvideo AJAX Action

Q: Who can exploit this issue?

An attacker needs an authenticated WordPress account with at least Subscriber-level access. No user interaction is required, and the vulnerable action is network-accessible through the plugin's AJAX functionality.

Q: Are sites affected if subscribers are not supposed to be able to import videos?

Yes. Subscriber access is intentionally forbidden from importing videos by the plugin's role-rights system, but the affected AJAX handler does not enforce that restriction. Any site that permits Subscriber-level accounts is therefore potentially exposed.

Q: What can an attacker do after exploiting it?

They can initiate video imports using the site owner's Infomaniak API credentials, potentially consuming the site's VOD account quota. They can also add arbitrary rows to the wp_vod_upload table so public shortcodes resolve to video content chosen by the attacker.

Q: How can I tell whether my site is affected?

The issue affects VOD Infomaniak versions up to and including 1.5.15. Review whether the plugin is installed at one of those versions and inspect the wp_vod_upload table and video-import activity for unexpected entries or imports.

Published Nov 6, 2026

Updated

The VOD Infomaniak plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.5.15. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to initiate unauthorized video imports using the site owner's Infomaniak API credentials, consume the site owner's VOD account quota, and insert arbitrary rows into the wpvodupload table causing public shortcodes to resolve to attacker-chosen video content. This action is explicitly reserved for Contributor-level and above by the plugin's own role-rights system, meaning subscriber access is intentionally forbidden by design — the AJAX handler simply omits the enforcement.

Event History

Nov 6, 2026

CVE Published

via MITRE·09:38 AM

Data Sourced

via MITRE·09:38 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

An attacker needs an authenticated WordPress account with at least Subscriber-level access. No user interaction is required, and the vulnerable action is network-accessible through the plugin's AJAX functionality.

Are sites affected if subscribers are not supposed to be able to import videos?

Yes. Subscriber access is intentionally forbidden from importing videos by the plugin's role-rights system, but the affected AJAX handler does not enforce that restriction. Any site that permits Subscriber-level accounts is therefore potentially exposed.

What can an attacker do after exploiting it?

They can initiate video imports using the site owner's Infomaniak API credentials, potentially consuming the site's VOD account quota. They can also add arbitrary rows to the wp_vod_upload table so public shortcodes resolve to video content chosen by the attacker.

How can I tell whether my site is affected?

The issue affects VOD Infomaniak versions up to and including 1.5.15. Review whether the plugin is installed at one of those versions and inspect the wp_vod_upload table and video-import activity for unexpected entries or imports.

CVE-2026-115831: VOD Infomaniak <= 1.5.15 - Missing Authorization to Authenticated (Subscriber+) Unauthorized Video Importation via vodimportvideo AJAX Action

Event History

Frequently Asked Questions

Who can exploit this issue?

Are sites affected if subscribers are not supposed to be able to import videos?

What can an attacker do after exploiting it?

How can I tell whether my site is affected?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Are sites affected if subscribers are not supposed to be able to import videos?

What can an attacker do after exploiting it?

How can I tell whether my site is affected?