NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

CVE-2021-3980 — elgg

HIGHFix: elgg/elgg@572d210

CVE-2021-3980 is a high-severity (CVSS 7.5) CWE-359 vulnerability in elgg/elgg. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for elgg/elgg — see the affected versions and patch details below.

Information exposure in elgg

Also known asGHSA-hx6g-q9v2-xh7v
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk
0.14%0.79%1.45%2.10%0.6%1.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐘elgg/elgg🐘elgg/elgg

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

elgg is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor. Forms in the view namespace 'forms/admin' were not protected by an AdminGatekeeper in case of AJAX requests to 'ajax/form/admin/'.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistelgg/elggall versions3.3.23composer require elgg/elgg:^3.3.23
🐘Packagistelgg/elgg≥ 4.0.0&&< 4.0.54.0.5composer require elgg/elgg:^4.0.5

Affected Products

1 product · 1 configurations
Application
elggelgg
< 3.3.23
range
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 elgg/elgg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update elgg/elgg to 3.3.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3980 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.

Frequently Asked Questions

elgg is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor. Forms in the view namespace 'forms/admin' were not protected by an AdminGatekeeper in case of AJAX requests to 'ajax/form/admin/'.
O3 Security · Impact-Aware SCA

Is CVE-2021-3980 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2021-3980: elgg — Fixed in 3.3.23