This vulnerability isn't a missing authorization check — it's the quiet elevation of a non-security feature into an authorization primitive without anyone noticing the trust boundary crossing. The Users_affiliations table was built to track referral relationships, likely for bonuses or social features. It was designed under assumptions of non-adversarial input: no cryptographic proof of consent, no server-side timestamp generation, no cross-user verification. That was appropriate for its original purpose. The failure occurred when someone later implemented video ownership reassignment and reached for the existing 'consented' flag without asking who set that flag or whether it could be forged. The commit diff that connects these two features is the actual crime scene — it shows the moment a developer trusted a non-security-grade signal for a security-critical operation. The client-supplied timestamp vulnerability is the exploit vector, but it's symptomatic of a deeper pattern: the original feature's design decisions were never annotated with security context in version control, so future developers had no way to know this field was never meant to cross a trust boundary. The blast radius extends forward, not just backward. Any developer in 2026 who builds a new security-relevant feature in AVideo and sees status='a' in the users_affiliations table will assume it's a valid authorization signal — because that's what the existing codebase already teaches them. The affiliation table now functions as a persistent contamination of the trust model, an active teaching tool that will generate future vulnerabilities until its role in authorization is either decommissioned or rebuilt with adversarial input assumptions from the ground up. The fix will likely add server-side timestamp validation, but that patch addresses only one detonation path. The table itself remains entropy in database form, and any new field added by the patch will itself become the next implicit trust signal for a future developer who needs a 'server-authoritative' timestamp. Organizations should audit which downstream subsystems currently treat affiliation consent as authorization, treat the table as a deprecated authorization primitive pending redesign, and encode security annotations directly in version control metadata so that future developers can see which fields were never designed to resist forgery.
CVE-2026-58002
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWWBN AVideo through commit 9c39d8c8b4c1f75540788d6b391740852ceb0732 contains an authorization bypass vulnerability in the Users_affiliations add.json.php endpoint that allows authenticated users to forge two-party consent records by supplying the counterparty's agreement timestamp. Attackers can create a forged affiliation with status='a' and then reassign video ownership to arbitrary users through the videoAddNew.json.php endpoint, which trusts the forged affiliation as an authorization term.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis vulnerability isn't a missing authorization check — it's the quiet elevation of a non-security feature into an authorization primitive without anyone noticing the trust boundary crossing. The Users_affiliations table was built to track referral relationships, likely for bonuses or social features. It was designed under assumptions of non-adversarial input: no cryptographic proof of consent, no server-side timestamp generation, no cross-user verification. That was appropriate for its original purpose. The failure occurred when someone later implemented video ownership reassignment and reached for the existing 'consented' flag without asking who set that flag or whether it could be forged. The commit diff that connects these two features is the actual crime scene — it shows the moment a developer trusted a non-security-grade signal for a security-critical operation. The client-supplied timestamp vulnerability is the exploit vector, but it's symptomatic of a deeper pattern: the original feature's design decisions were never annotated with security context in version control, so future developers had no way to know this field was never meant to cross a trust boundary. The blast radius extends forward, not just backward. Any developer in 2026 who builds a new security-relevant feature in AVideo and sees `status='a'` in the users_affiliations table will assume it's a valid authorization signal — because that's what the existing codebase already teaches them. The affiliation table now functions as a persistent contamination of the trust model, an active teaching tool that will generate future vulnerabilities until its role in authorization is either decommissioned or rebuilt with adversarial input assumptions from the ground up. The fix will likely add server-side timestamp validation, but that patch addresses only one detonation path. The table itself remains entropy in database form, and any new field added by the patch will itself become the next implicit trust signal for a future developer who needs a 'server-authoritative' timestamp. Organizations should audit which downstream subsystems currently treat affiliation consent as authorization, treat the table as a deprecated authorization primitive pending redesign, and encode security annotations directly in version control metadata so that future developers can see which fields were never designed to resist forgery.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data