Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

CVE-2021-3850

CRITICALFix: adodb/adodb@952de6c

CVE-2021-3850 is a critical-severity (CVSS 9.1) CWE-305 vulnerability in adodb/adodb-php. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2021-3850 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Authentication Bypass in ADOdb/ADOdb

Also known asGHSA-65mj-7c86-79jf
Published
Jan 25, 2022
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Real-World Exposure

2 pkgs affected
🐘adodb/adodb-php🐘adodb/adodb-php

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Authentication Bypass by Primary Weakness in GitHub repository adodb/adodb prior to 5.20.21.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistadodb/adodb-phpall versions5.20.21
🐘Packagistadodb/adodb-php5.21.0&&< 5.21.45.21.4
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for adodb/adodb-php. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update adodb/adodb-php to 5.20.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3850 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-3850 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-3850. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Authentication Bypass by Primary Weakness in GitHub repository adodb/adodb prior to 5.20.21.
O3 Security · Impact-Aware SCA

Is CVE-2021-3850 in your dependencies?

O3 detects CVE-2021-3850 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.