dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45714

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
CubeCart is an ecommerce software solution. Prior to 6.7.0, an Authenticated Server-Side Template Injection (SSTI) vulnerability exists in multiple modules of CubeCart (including Email Templates, Invoices, Documents, and Contact Forms). The application unsafely evaluates user-supplied input using the Smarty template engine without enabling Smarty Security Policies. This allows any authenticated user with administrative privileges to execute arbitrary operating system commands (RCE) on the server. This vulnerability is fixed in 6.7.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 · high confidence

An authenticated Server-Side Template Injection (SSTI) vulnerability in CubeCart versions prior to 6.7.0 allows users with administrative privileges to execute arbitrary operating system commands by injecting malicious payloads into the Smarty template engine. The vulnerability exists in multiple modules (Email Templates, Invoices, Documents, and Contact Forms) because the application evaluates user-supplied input without enabling Smarty Security Policies.

MitigationUpgrade CubeCart to version 6.7.0 or later, which implements Smarty Security Policies to prevent template injection attacks. Verify that all affected modules are patched and consider reviewing administrative user accounts for 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 CubeCart installation and version
    Locate the CubeCart installation directory and check the version file (commonly includes a version.php, changelog, or admin/includes/config.php file that displays the software version)
    Affected if The installed version is prior to 6.7.0 (e.g., 6.5.x, 6.6.x)
  2. Confirm administrative access exists
    Review user accounts in the database (typically in the admin_users orCubeCart_admin table) to determine if any administrative-level accounts exist
    Affected if Any administrative user account is present in the system (the vulnerability requires admin privileges)
  3. Verify affected modules are present
    Check for the presence of Email Templates, Invoices, Documents, and Contact Forms modules in the CubeCart admin panel or installation directory under the modules folder
    Affected if Any of these modules (Email Templates, Invoices, Documents, Contact Forms) are installed and accessible in the admin interface
  4. Inspect Smarty template configuration
    Locate the Smarty configuration file (typically in admin/includes/ or includes/lib/ folder) and check if Smarty Security Policies are enabled (look for $smarty->enableSecurity() or $security_settings array)
    Affected if Smarty Security Policies are NOT enabled in the template configuration

A system is affected if it runs CubeCart versions prior to 6.7.0 with administrative access available and has the vulnerable modules present without Smarty Security Policies configured.

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

Upgrade CubeCart to version 6.7.0 or later, which implements Smarty Security Policies to prevent template injection attacks. Verify that all affected modules are patched and consider reviewing administrative user accounts for compromise.

Recommended fix High confidence

6.7.0

  1. 1. Backup your existing CubeCart installation including all files, database, and configuration.
  2. 2. Download CubeCart version 6.7.0 from the official CubeCart website or their official GitHub repository.
  3. 3. Review the official CubeCart upgrade documentation for version 6.7.0 to understand any specific upgrade requirements.
  4. 4. Upload the new version 6.7.0 files to your server, overwriting the existing installation.
  5. 5. Run any database migration scripts included in the 6.7.0 release if required.
  6. 6. Verify the upgrade was successful by logging into the admin panel.
  7. 7. Test critical functionality (especially the modules mentioned: Email Templates, Invoices, Documents, and Contact Forms) to ensure they work correctly.
  8. 8. Verify that Smarty Security Policies are properly configured in the updated version.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45714 — 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-2026-45714 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