/

CVE-2026-25811

Severity:

CRITICAL RISK

(9.1)

Improper Authorization in PlaciPy Placement Management

CVE-2026-25811

Analyzed

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-863

Impact:

Cross-Tenant Data Access and Unauthorized Data Exposure

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

PlaciPy 1.0.0 derives a tenant identifier directly from the user's email domain without confirming that the user actually owns or belongs to that domain.

This design flaw can allow a malicious user to impersonate another tenant's domain and gain cross-tenant access to data belonging to other institutions.

Affected context

The vulnerability occurs in PlaciPy's multi-tenant environment where tenants (typically educational institutions) are logically separated based on a tenant identifier.

In version 1.0.0, the tenant ID is implicitly derived from the email domain submitted by a user during registration or login, and the system assumes that this email domain is trustworthy without verifying domain ownership or enrollment policies.

Any deployment where tenant isolation is keyed off email domains rather than explicit, verified tenant associations may be exposed to cross-tenant data access.

Exploit preconditions

  • Attack surface: Public-facing authentication/registration or account creation flows where email addresses are supplied by end users.
  • Required access: Ability to sign up or modify an account using a crafted email address with a chosen domain (no prior compromise of the target tenant is required).
  • Trigger point: Providing an email address whose domain matches (or is interpreted as matching) a different tenant's domain, causing the application to associate the attacker with that tenant.
  • Why exploitation is possible: The authorization model implicitly trusts email domains as proof of tenant membership, with no independent verification of domain ownership, institutional affiliation, or explicit tenant mapping.

Why this happens

This issue stems from an authorization design that uses an unvalidated, user-controlled attribute (the email domain) as the authoritative source for tenant identity.

Instead of binding users to tenants through server-side, verified relationships (e.g., admin-approved enrollment, domain verification, or invitation flows), the system infers tenant membership directly from client-supplied input.

This aligns with CWE-863: Improper Authorization, where the application makes access control decisions based on assumptions about user attributes that have not been securely established, allowing attackers to bypass tenant isolation guarantees.

Potential impact

  • Attackers may access data belonging to other educational institutions within the same PlaciPy deployment.
  • Unauthorized viewing of student records, placement details, or institution-specific reports.
  • Potential modification or deletion of data for another tenant if write operations are scoped only by tenant ID.
  • Misrepresentation or corruption of placement information, impacting institutional trust and compliance obligations.
  • Escalation from a low-privileged account to effective access across multiple tenants, undermining the multi-tenant security model.

General mitigation guidance

Effective mitigation focuses on tightening tenant association and separating identity from untrusted input:

  • Use explicit, server-managed tenant mappings rather than inferring tenant identity from the email domain alone.
  • Require a robust tenant enrollment process, such as administrator approval, invite-based onboarding, or verified domain ownership before associating accounts with institutions.
  • Implement strict authorization checks that validate both user identity and tenant membership on every tenant-scoped operation, not just at login.
  • Treat email addresses and domains as untrusted attributes for display and communication, not as security boundaries or access-control keys.
  • Apply least-privilege principles so that new accounts start with minimal access until their tenant relationship is confirmed.
  • Consider enforcing additional verification factors (e.g., out-of-band confirmation via institution-controlled channels) before granting access to tenant-wide data.

How teams detect issues like this

Detection typically involves reviewing both code and behavior for authorization weaknesses:

  • Code review: Look for logic that maps email or email_domain fields directly to tenant IDs or roles without intermediate verification, especially in authentication, registration, and tenant resolution components.
  • Static analysis: Configure rules to flag access-control decisions based on user-controlled attributes (e.g., email domain, query parameters) instead of verified tenant associations or server-side lookups.
  • Authorization testing: Conduct multi-tenant penetration tests where users attempt to access resources of other tenants by altering email domains, tenant parameters, or session attributes.
  • Logging and monitoring: Instrument logs to track tenant context in each request and alert on anomalous patterns, such as a single account appearing under multiple tenant contexts or unusual cross-tenant access patterns.
  • Automated security review tools can be integrated into CI/CD to detect patterns where tenancy is inferred from user input rather than from trusted internal references.

Sources

SourceLink
github.comgithub.com/Praskla-Technology/assessment-placipy/security/advisories/GHSA-3gmm-9ww2-87fh

Frequently asked

questions

In environments where users can freely register or change their email addresses, this issue can often be exploited by any attacker who can guess or know the email domain of a target tenant. The broader and more open the registration process, the wider the exploitability.

Typically only the ability to create or modify an account with a chosen email address within the affected PlaciPy deployment. No prior access to the target tenant's systems is required if tenant membership is inferred solely from the email domain.

Decouple tenant identity from email domains and other user-supplied fields. Introduce a server-side tenant mapping model that explicitly binds users to tenants through verified processes (such as invitations, admin approval, or domain ownership verification), and enforce tenant-aware authorization checks on all data access paths.

Treat multi-tenancy as a core security boundary: design tenant isolation explicitly, avoid inferring authorization from user-controlled attributes, and enforce consistent authorization checks on every resource access. Incorporate security reviews, threat modeling, and automated checks focused on access control and tenant isolation early in the design and development lifecycle.

Find out what's already
exploitable in your codebase.