# AVideo has Pre-Captcha User Enumeration and Account Status Disclosure in Password Recovery Endpoint

Advisory record · `GHSA-m99f-mmvg-3xmx`

- **Identifiers:** `GHSA-m99f-mmvg-3xmx` · `CVE-2026-33688` · `PKSA-rmrd-1jny-519s`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-204](https://cwe.mitre.org/data/definitions/204.html)
- **Tags:** [CWE-204](https://agentprime.io/advisories/tag/cwe-204.md)
- **Published:** 25 Mar 2026
- **Updated:** 25 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Mar 2026, 19:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wwbn/avideo` (Packagist): affected `<=26.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The AVideo package wwbn/avideo, versions up to and including 26.0, has a password recovery endpoint (objects/userRecoverPass.php) that checks whether a username exists and whether the account is active before validating the captcha. An unauthenticated remote attacker can send repeated requests without solving a captcha and use the distinct error responses to enumerate valid usernames and tell active, inactive and nonexistent accounts apart. No fixed version is listed, and the source gives no workaround.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m99f-mmvg-3xmx)

## Sources

- [GitHub Advisory Database: GHSA-m99f-mmvg-3xmx](https://github.com/advisories/GHSA-m99f-mmvg-3xmx)
- [OSV: GHSA-m99f-mmvg-3xmx](https://osv.dev/vulnerability/GHSA-m99f-mmvg-3xmx)
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-m99f-mmvg-3xmx>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33688>
- <https://github.com/WWBN/AVideo/commit/e42f54123b460fd1b2ee01f2ce3d4a386e88d157>
- <https://github.com/WWBN/AVideo>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m99f-mmvg-3xmx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m99f-mmvg-3xmx/>. Everything for agents: <https://agentprime.io/llms.txt>.