Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-8vq6-5f66-hp3r

MEDIUMFix: dolibarr/dolibarr@4973019

GHSA-8vq6-5f66-hp3r is a medium-severity (CVSS 4.3) CWE-840 vulnerability in dolibarr/dolibarr. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-8vq6-5f66-hp3r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Logic error in dolibarr/dolibarr

Also known asBIT-dolibarr-2022-0746CVE-2022-0746
Published
Feb 26, 2022
Updated
Apr 3, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Apr 3, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘dolibarr/dolibarr

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

In dolibarr/dolibarr prior to 16.0 any low privileged users could update their login name which should only be updated by admin.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistdolibarr/dolibarrall versions16.0
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 dolibarr/dolibarr. 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 dolibarr/dolibarr to 16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8vq6-5f66-hp3r 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 GHSA-8vq6-5f66-hp3r 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 GHSA-8vq6-5f66-hp3r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In dolibarr/dolibarr prior to 16.0 any low privileged users could update their login name which should only be updated by admin.
O3 Security · Impact-Aware SCA

Is GHSA-8vq6-5f66-hp3r in your dependencies?

O3 detects GHSA-8vq6-5f66-hp3r across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-8vq6-5f66-hp3r: Logic error in… | O3 Security