Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-53761 – Authentication Bypass – Frappe CRM before 1.73.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-53761 is an authentication bypass vulnerability (CWE-287: Improper Authentication) affecting Frappe CRM, the open-source CRM application built on the Frappe framework. The flaw stems from user invitation keys that remain valid and logged/accessible even after the associated account has already accepted the invitation, allowing an attacker who obtains a previously-used invitation key to authenticate as that user. The issue carries a high severity rating (CVSS 8.2).

Technical details

  • Root cause: Invitation keys issued by Frappe CRM’s crm/api invitation flow are not invalidated (nulled) after a user accepts the invitation and activates their account.
  • Trigger condition: Any deployment of Frappe CRM that has issued user invitations is potentially exposed — the invitation key for an already-accepted invite can still be used to gain access.
  • Attack vector: Network — no authentication or user interaction is required by the victim; an attacker only needs to obtain a previously logged/used invitation key.
  • Impact: Unauthorized access to a legitimate user account, resulting in a high impact to data/session integrity (account takeover of previously invited accounts).

Affected software

  • Frappe CRM versions prior to v1.73.0 (advisory also references versions prior to v1.72.1 as vulnerable)
  • Fixed in v1.73.0 and later

Severity

  • CVSS Score: 8.2 (High)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Frappe CRM to v1.73.0 or later, which nullifies the invitation key once it has been accepted and introduces a "pending" invitation status.
  • If unable to patch immediately: Manually run a script or SQL command to nullify/randomize the key field for all rows in the tabCRM Invitation table where the status is already "Accepted," to invalidate any previously usable invitation keys.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named meta tag generator: frappe

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge