CVE-2025-64707
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrappe Learning is a learning system that helps users structure their content. Starting in version 2.0.0 and prior to version 2.41.0, when admins revoked a role from the user, the effect was not immediate because of caching. The issue has been fixed in version 2.41.0 by ensuring the cache is cleared after roles are updated.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFrappe Learning versions 2.0.0 through 2.41.0 have a broken access control vulnerability where role revocation via admin action does not take effect immediately due to improper cache invalidation. Users with revoked roles retain permissions based on stale cached role data until the cache expires naturally.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, < 2.41.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Frappe Learning versionQuery the Frappe bench or application metadata to retrieve the installed version of Frappe Learning. Common methods include: bench get-app version frappe_learning, checking the app's version.py file in the Frappe bench/apps directory, or querying the installed_apps table in the Frappe database.Affected if The installed version is >= 2.0.0 and < 2.41.0, placing it within the vulnerable range.
-
Verify role management is in useCheck if Frappe Learning's role-based access control features are actively configured. Inspect the User document type and associated roles within the Frappe system, specifically looking for roles assigned that originate from the Frappe Learning app.Affected if Frappe Learning roles are assigned to users in the system, meaning the stale cache issue could allow revoked permissions to persist.
-
Test for stale permission persistence after role revocationAs an administrator, revoke a role from a user via Frappe's admin interface (such as the User form or the 'Update Roles' action). Immediately attempt to access a resource or feature that should be restricted without that role. Compare behavior against expected denial.Affected if The revoked user can still access resources they should no longer have permission for, indicating stale cached role data is in effect.
-
Inspect role permission cache settingsExamine the Frappe cache configuration for session and role-related cache entries. Check the cached user roles in the Redis or database cache (frappe_cache keys containing 'user_roles' or similar patterns) to see how long role data persists.Affected if Role permission cache entries have a long TTL or no invalidation trigger, allowing stale data to remain beyond the expected immediate revocation period.
A system is affected if Frappe Learning version 2.0.0 to 2.41.0 is installed with active role assignments, and users retain access after role revocation due to uncached permission data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.41.0
Upgrade to Frappe Learning version 2.41.0 or later, which implements proper cache clearing after role updates. Verify that role revocation now takes effect immediately.
2.41.0
- Upgrade Frappe Learning to version 2.41.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64707 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data