CVE-2025-68929
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 is a full-stack web application framework. Prior to versions 14.99.6 and 15.88.1, an authenticated user with specific permissions could be tricked into accessing a specially crafted link. This could lead to a malicious template being executed on the server, resulting in remote code execution. Versions 14.99.6 and 15.88.1 fix the issue. No known workarounds are available.
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 framework versions prior to 14.99.6 and 15.88.1 contain a Server-Side Template Injection (SSTI) vulnerability. An authenticated user with specific permissions can be tricked via a specially crafted link into triggering malicious template execution, leading to arbitrary remote code execution on the server.
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< 14.99.6>= 15.0.0, < 15.88.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 Frappe installationLocate the Frappe framework installation directory, typically found at /home/frappe/frappe-bench or check for frappe executable in PATH using 'which frappe' or 'frappe --version'Affected if Frappe framework is not installed on the system
-
Determine installed Frappe versionRun 'bench version' from the Frappe bench directory, or check the version file in the Frappe installation (e.g., cat apps/frappe/frappe/__init__.py | grep __version__')Affected if The installed version cannot be determined or the command fails
-
Compare version against affected rangesCheck if version is less than 14.99.6 for the 14.x branch, or greater than or equal to 15.0.0 but less than 15.88.1Affected if Installed version falls within < 14.99.6 or >= 15.0.0, < 15.88.1
-
Verify authentication is enabledConfirm that Frappe's user authentication system is active by checking the site configuration file (sites/{sitename}/site_config.json) for 'db_name' and 'admin_password' or by accessing the login pageAffected if User authentication is enabled (which is default) - the vulnerability requires an authenticated user to trigger it
A system is affected if Frappe framework is installed and the installed version falls below 14.99.6 or between 15.0.0 and 15.88.1, with user authentication enabled.
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 · scoped14.99.615.88.1
Upgrade Frappe to version 14.99.6 or 15.88.1 (or later) to patch the template injection vulnerability. No workarounds are available.
14.99.6+ for 14.x branch, or 15.88.1+ for 15.x branch
- Identify the currently running Frappe version using `bench version` or checking your requirements.txt
- For Frappe 14.x branch: Upgrade to version 14.99.6 or later by running `bench switch-to-branch version-14` followed by `bench update --patch`
- For Frappe 15.x branch: Upgrade to version 15.88.1 or later by running `bench switch-to-branch version-15` followed by `bench update --patch`
- After upgrade, verify the new version is installed using `bench version`
- Restart all Frappe/ERPNext services to ensure the patched code is loaded: `bench restart`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68929 — 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-68929 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