On this page (7 sections)
A critical authentication bypass has been published for WWBN AVideo, the open source video sharing platform. According to the NVD record for CVE-2026-126542, an unauthenticated attacker can log in as any user, including an administrator, without a password by setting a social login display name to match the victim's username.
If you run a self-hosted AVideo site, especially one with X, Facebook, Yahoo or LinkedIn login enabled, treat this as urgent. The only description of the flaw available so far is the NVD record, so details beyond it are marked as unconfirmed below.
What happened
The CVE record, published on 2026-11-11, describes an authentication bypass in the way AVideo handles logins through Hybridauth, a library that connects sites to social networks. Per the record, an attacker sets the display name of their own X, Facebook, Yahoo or LinkedIn account to a victim's AVideo username and withholds their email address. That causes login.json.php or oauth2.php to log them in as the victim's account, administrators included, with no password.
The record's references include source files for login.json.php and plugin/MobileManager/oauth2.php at v29.7.1, a GitHub commit, a GitHub security advisory and a VulnCheck advisory. The research only lists these as references and does not include their contents. Only one independent publisher covers the story so far, so treat anything beyond the CVE description as unconfirmed.
What this weakness class means
The flaw is classed as CWE-290, an authentication bypass by spoofing. In general terms, a display name is a label that anyone can edit on their own social profile, so it should never be used on its own to decide which local account a visitor is. A safer design ties a social login to a stable identifier verified by the provider. This is general background on the weakness class; the research does not describe AVideo's internal logic beyond the record's description.
The record's impact statement is simple: no password is needed, and the target can be any user, including an administrator. What an attacker could do after logging in depends on what that account can do on your site, and the research does not describe specific post-login actions.
Who is exposed
- Operators of self-hosted AVideo installations running any version from 6.5 through 29.7.1.
- Sites where social login through Hybridauth with X, Facebook, Yahoo or LinkedIn is enabled, since the record describes the attack through those providers.
- Any deployment where login.json.php or oauth2.php, the two code paths the record names, is reachable. The research does not say which configurations or plugins must be enabled for the flaw to be reachable, so verify your own setup rather than assume you are safe.
- Agencies and hosts that run AVideo for clients and may not track its version.
How to check your exposure
First find out which version you run. The admin area may show it, and you can also check your installation files. If you installed from Git, this read-only command, run in the AVideo directory, prints the current tag or commit. Compare the result with the affected range of 6.5 through 29.7.1:
git describe --tags --alwaysNext, look in your web server logs for requests to the two files named in the CVE record. This read-only search, run on the server, prints the 200 most recent matching lines. The path below is a common default for Apache on Debian/Ubuntu, so adjust it for your server. Look for unusual bursts of requests or logins that precede unexpected admin activity:
grep -E "login\.json\.php|oauth2\.php" /var/log/apache2/access.log | tail -n 200Also review the user list in the admin panel for accounts you do not recognize, recent changes to administrator accounts, and any unexpected new plugins, settings or uploaded files.
What to do now
- Identify every AVideo installation you run and note its version.
- Open the GitHub advisory GHSA-9rvm-cfc4-q9g9 and the other references in the CVE record to find out which release addresses the issue, then upgrade to it. The research does not name a fixed version, so confirm it yourself.
- As a precaution until you can upgrade, consider disabling social login through X, Facebook, Yahoo and LinkedIn if you do not need it. This is general risk reduction, not a vendor-recommended mitigation from the research.
- Review recent logins, administrator accounts and recent admin activity for signs of takeover.
- If you suspect abuse, change administrator passwords, review API keys and secrets stored in the application, and invalidate active sessions.
- Restrict access to the admin area by IP address or VPN where practical.
- Take a backup before upgrading, and test the site afterwards, including social login.
Detection and monitoring afterwards
Keep watching for signs of account takeover even after you patch, since an attacker may have acted before the fix. Alert on new administrator accounts, changes to user roles, logins from unusual countries or at odd hours, and new files in upload or plugin directories. A web application firewall can add a filtering layer in front of login endpoints, but it is not a substitute for patching; see what a WAF is for what it can and cannot do.
If you manage several sites, Webforta Monitor can watch uptime, certificates, DNS and header changes, which helps you notice unexpected changes to a public site. For a wider check of whether a site has been tampered with, see how to check if a website is hacked, and if you find evidence of compromise, follow website hacked: what to do.
What is still unknown
- The fixed version is not stated in the research; confirm it from the advisory and other references.
- No source in the research reports active exploitation, and the CISA Known Exploited Vulnerabilities field in the research data is empty. That means no known exploitation, not proof of safety.
- Only one independent publisher covers this story so far, and the research contains no content from the GitHub or VulnCheck advisories, so details may be refined as more analysis appears.
- Which configurations are reachable, for example whether sites with social login disabled are affected, is not stated.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
