# CVE-2026-43877: AVideo: CSRF in userSavePhoto.php Allows Cross-Origin Overwrite of Authenticated Users' Profile Photos with Arbitrary Content

> Attacker can overwrite any logged-in user's profile photo with arbitrary bytes via CSRF due to missing token validation and SameSite=None cookies.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-jw8g-5j46-44rp

## What is CVE-2026-43877?

CVE-2026-43877 is a medium-severity vulnerability in WWBN AVideo, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

WWBN AVideo is an open source video platform. In versions up to and including 29.0, objects/userSavePhoto.php is a legacy profile-photo endpoint that accepts a base64 POST parameter and writes the decoded bytes to videos/userPhoto/photo<users_id>.png. Its only access control is User::isLogged(). It does not end in .json.php, so it is excluded from the project's global autoCSRFGuard (which is suffix-scoped in objects/include_config.php). There is no CSRF token, no Origin/Referer check, and no MIME validation of the decoded bytes. Because AVideo's default cookie policy is SameSite=None; Secure on HTTPS (objects/functionsPHP.php:227), an attacker who lures a logged-in user to a malicious page can overwrite that user's profile photo with arbitrary bytes and also triggers a site-wide clearCache(true) on every forged request. Commit 9c38468041505e637101c5943c5370c68f48e3ac contains an updated fix.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-43877?

2 open source packages ship an affected version, including wwbn/avideo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |

## How do I fix CVE-2026-43877?

No fix has been published for CVE-2026-43877 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43877 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43877 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43877 and fix it if it is affected.

What it is: CVE-2026-43877 is a medium-severity vulnerability in WWBN AVideo, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43877 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 29.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 29.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43877/ (Markdown: https://insights.sbomify.com/CVE-2026-43877/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43877
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43877
- OSV: https://osv.dev/vulnerability/CVE-2026-43877

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43877/
Summaries are generated and may contain mistakes; the official description above is the record.
