Security readout for executives and security teams
Plain-English summary
AnythingLLM had a password recovery behavior that could reveal whether a username exists. An attacker could use this to build a list of valid accounts, increasing phishing, password-spraying, or targeted login attack risk. The issue is fixed in commit e287fab56089cf8fcea9ba579a3ecdeca0daa313.
Executive priority
Treat this as a moderate-priority identity exposure issue. It does not directly compromise accounts, but it can make credential attacks more efficient. Prioritize internet-facing AnythingLLM instances and environments with sensitive user populations.
Technical view
CVE-2026-21484 affects Mintplex-Labs anything-llm before commit e287fab56089cf8fcea9ba579a3ecdeca0daa313. The password recovery endpoint returned different error messages for existing versus non-existing usernames, causing username enumeration. It is classified under CWE-203 and CWE-204 with CVSS 3.1 score 5.3, network exploitable, no authentication required.
Likely exposure
Exposure applies to AnythingLLM deployments running code prior to commit e287fab56089cf8fcea9ba579a3ecdeca0daa313, especially where the password recovery endpoint is reachable over a network or the internet.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. The flaw requires no authentication and low attack complexity, but it discloses only account-existence information rather than granting direct access.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, and fixing commit. No exploit publication or active exploitation is cited in the provided sources. The key validation point is whether password recovery response handling includes the fixing commit.
Mitigation direction
- Upgrade or update AnythingLLM to include commit e287fab56089cf8fcea9ba579a3ecdeca0daa313.
- Review the GitHub advisory for vendor guidance and any release mapping.
- Restrict unnecessary external access to password recovery functions where operationally feasible.
- Monitor authentication and password recovery activity for abnormal volume or targeting.
Validation and detection
- Inventory AnythingLLM deployments and identify their deployed commit or release lineage.
- Confirm whether deployed code predates commit e287fab56089cf8fcea9ba579a3ecdeca0daa313.
- Verify password recovery responses are uniform for valid and invalid usernames.
- Check logs for unusual password recovery requests or repeated username probing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-204: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-21484 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-47vr-w3vm-69chCVE reference · x_refsource_CONFIRM
- https://github.com/Mintplex-Labs/anything-llm/commit/e287fab56089cf8fcea9ba579a3ecdeca0daa313CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Observable Response Discrepancy
Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.