LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32691: Auto-merging Person Records Compromised

Apollos Apps is an open source platform for launching church-related apps. In Apollos Apps versions prior to 2.20.0, new user registrations are able to access anyone's account by only knowing their basic profile information (name, birthday, gender, etc). This includes all app functionality within the app, as well as any authenticated links to Rock-based webpages (such as giving and events). There is a patch in version 2.20.0. As a workaround, one can patch one's server by overriding the `create` data source method on the `People` class.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Older Apollos Apps versions can incorrectly merge a new registration into someone else’s person record when basic profile details match. That can expose the other user’s app account and authenticated Rock links, including giving and events. Version 2.20.0 contains the vendor patch.

Executive priority

Treat as high priority for any church or organization using vulnerable Apollos Apps. The business risk is account takeover and exposure of sensitive member functions, not merely a crash or service issue. Patch status should be verified promptly.

Technical view

CVE-2021-32691 affects Apollos Apps before 2.20.0. The registration auto-merge logic could let an unauthenticated new registrant gain another account’s privileges using basic profile information. The source bundle maps this to CWE-303 and CVSS 8.8 high severity.

Likely exposure

Exposure is limited to organizations running Apollos Apps versions earlier than 2.20.0, especially deployments integrated with Rock-based authenticated webpages. The source bundle does not identify affected hosted services beyond ApollosProject apollos-apps.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not listed as KEV. The advisory describes a low-complexity registration-path account compromise requiring user interaction, but no exploit code or campaign evidence is provided.

Researcher notes

Focus analysis on registration auto-merge behavior and identity binding around person records. Evidence supports vulnerable versions, patch availability, and workaround direction, but not public exploitation. Keep validation controlled and avoid testing against real member accounts without authorization.

Mitigation direction

  • Upgrade Apollos Apps to version 2.20.0 or later.
  • If upgrade is delayed, apply the vendor-described People create method override workaround.
  • Review vendor advisory and release notes before production rollout.
  • Reassess Rock authenticated links exposed through the app after remediation.

Validation and detection

  • Inventory Apollos Apps deployments and confirm versions are 2.20.0 or later.
  • Check whether any temporary People create override is present and documented.
  • Review registration and person-merge logs for suspicious merges before remediation.
  • Confirm authenticated app and Rock links map to the intended user identity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-303: 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 lookup
cve · low confidence lookup

CVE-2021-32691 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-32691Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ApollosProjectapollos-apps< 2.20.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-303 · source CWE mapping

Incorrect Implementation of Authentication Algorithm

Incorrect Implementation of Authentication Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.