Authorization Flaw in Frappe (CVE-2025-66581)
Summary
Vulnerability in Frappe (CVE-2025-66581). Data can be tampered with by attackers. Mitigation: upgrade to 2.41.0 or later.
Original description
The description as published by the source.
Frappe Learning Management System (LMS) is a learning system that helps users structure their content. Prior to 2.41.0, a flaw in the server-side authorization logic allowed authenticated users to perform actions beyond their assigned roles across multiple features. Because the affected endpoints relied on client-side or UI-level checks instead of enforcing permissions on the server, users with low-privileged roles (such as students) could perform operations intended only for instructors or administrators via directly using the API's. This vulnerability is fixed in 2.41.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-66581 has been found in Frappe.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade Frappe to 2.41.0 or later.
If unsure, ask your IT team or search "Frappe CVE-2025-66581" on the vendor's site.
CVE-2025-66581 (Frappe) — CWE-863 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.41.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in Frappe.
Check the vendor advisory for the affected versions of Frappe.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 2.41.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Frappe' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Frappe' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Frappeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Frappe to 2.41.0ステージング環境で 2.41.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory security-advisories@github.com