Skip to main content

Placipy CVE-2026-25875

CRITICAL
Incorrect Authorization (CWE-863)
2026-02-09 security-advisories@github.com
9.8
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious JWT token
  2. Delivery
    Modify role and scope claims to admin
  3. Exploit
    Send authenticated request
  4. Execution
    Bypass authorization checks
  5. Impact
    Access admin functions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

PlaciPy version 1.0.0 with JWT authentication enabled. Admin authorization middleware must trust client-controlled JWT claims without server-side role verification. No authentication credentials required for initial token forgery.

Impact

CVSS 9.8.

Exploit ScenarioDerived

An attacker escalates privileges to admin level.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

PlaciPy has an incorrect authorization allowing privilege escalation — seventh and final critical vulnerability.

Earlier versions of this analysis (1)
v1 Mar 12, 2026 - 21:54 CVSS 9.8

Seventh PlaciPy authorization flaw enabling privilege escalation.

RemediationAI

PlaciPy 1.0.0 is not fit for any deployment. Seven critical vulnerabilities across auth, authz, and injection.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-863 in PlaciPy 1.0.0. Seven critical vulnerabilities make the application fundamentally broken from a security perspective.

Know when Placipy gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionGitHub Advisory

PlaciPy is a placement management system designed for educational institutions. In version 1.0.0, The admin authorization middleware trusts client-controlled JWT claims (role and scope) without enforcing server-side role verification.

Executive ViewAI

Why It Matters

CVE-2026-25875 is a critical authentication bypass vulnerability in PlaciPy 1.0.0 that allows attackers to forge administrative privileges by manipulating JWT tokens, potentially granting unauthorized access to student placement records and system administration functions. Educational institutions using this software face immediate risk of data breach, unauthorized modifications to placement decisions, and compliance violations affecting student privacy and institutional integrity.

Business Impact: Severe
Compensating Controls

Implement network segmentation to restrict PlaciPy access to authorized administrative staff only; deploy WAF rules to reject suspicious JWT claims with invalid role/scope values; enforce mutual TLS (mTLS) for all client connections; implement real-time JWT signature validation and claims verification at application entry points; enable comprehensive audit logging of all authentication attempts and administrative actions; consider disabling the placement management feature entirely until patch availability.

Threat Intelligence Overview

EPSS Score
0.1%
Top 81% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:prasklatechnology:placipy:1.0.0:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy