CVE-2026-92579: AVideo through 29.0 Broken Access Control via CSRF Exemption Basename Collision

Published Sep 16, 2026
·
Updated

In AVideo through 29.0, the autoCSRFGuard() function maintains a hardcoded allowlist of exempt basenames tested without directory context, allowing plugin files matching core filenames to inherit CSRF exemptions. The LoginWordPress plugin file login.json.php inherits an exemption and unconditionally logs out authenticated users on cross-site POST requests before validating credentials.

Affected Software

2 affected components
AVideo<=29.0
LoginWordPress plugin/login.json.php

Event History

Sep 16, 2026
CVE Published
via MITRE·09:46 PM
Data Sourced
via MITRE·09:46 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

AVideo installations through 29.0 that have the LoginWordPress plugin file login.json.php present are exposed. The affected behavior targets authenticated users, who can be logged out through a cross-site POST request.

2

What does an attacker need to exploit it?

An attacker does not need credentials, but must cause an authenticated user to submit or trigger a cross-site POST request to the affected plugin endpoint. User interaction is required.

3

What is the practical impact?

Successful exploitation unconditionally logs the authenticated user out before credentials are validated. The supplied severity vector indicates integrity and availability impact, with no confidentiality impact.

4

How can I determine whether my deployment is affected?

Check whether the deployment uses AVideo version 29.0 or earlier and whether the LoginWordPress plugin includes login.json.php. The issue depends on that plugin file receiving a CSRF exemption because its basename collides with an exempt core filename.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203