dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-26936

CRITICAL · 10.0 CVSS v3.1 Published 2025-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in FRESHFACE Fresh Framework fresh-framework allows Code Injection.This issue affects Fresh Framework: from n/a through <= 1.70.0.

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 · moderate confidence

Code injection vulnerability in FRESHFACE Fresh Framework (fresh-framework) allows attackers to inject and execute arbitrary server-side code. The vulnerability stems from improper control of code generation, likely due to insufficient input validation or unsafe use of dynamic code execution functions within the framework.

MitigationUpdate Fresh Framework to the latest version beyond 1.70.0 immediately; if no patched version exists, disable the framework or migrate to an alternative solution. Review application logs and file system for signs of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify fresh-framework installation
    Check your project's package.json dependencies section, or run 'npm list fresh-framework' or 'pip show fresh-framework' depending on the package manager used
    Affected if fresh-framework is listed in dependencies and the installed version is below 1.70.0
  2. Determine installed version
    Run the package manager show command for fresh-framework and note the exact version number reported
    Affected if The reported version is lower than 1.70.0
  3. Locate dynamic code generation usage
    Search your codebase for patterns such as eval(), new Function(), or similar runtime code construction methods that may use fresh-framework
    Affected if Dynamic code generation functions are present in code using fresh-framework
  4. Inspect user input flow to code generation
    Trace data flow from HTTP request parameters, form inputs, or API payloads into any eval(), new Function(), or similar constructs used with fresh-framework
    Affected if Unsantitized user-controllable data flows directly into dynamic code creation functions

You are affected if fresh-framework version is below 1.70.0 AND your application uses dynamic code generation with unsanitized user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Fresh Framework to the latest version beyond 1.70.0 immediately; if no patched version exists, disable the framework or migrate to an alternative solution. Review application logs and file system for signs of compromise.

Recommended fix Moderate confidence

Latest available Fresh Framework version (after 1.70.0)

  1. Check your current Fresh Framework version in WordPress admin under Plugins
  2. If running version 1.70.0 or lower, update to the latest available version of Fresh Framework
  3. Verify the update completed successfully
  4. Test that site functionality remains intact after update
  5. Review changelog or release notes if available for any security-related fixes
Caveat Review plugin changelog before upgrading as customizations may be affected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26936 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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