dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45708

HIGH · 7.2 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 →
78/100
Remediation priority · High
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.3, an admin with documents edit permission can save raw <?php … ?> into the Invoice Editor. The next time any admin clicks Print on any order, the rendered template is written to files/print.<md5>.php. files/.htaccess ships an explicit <Files print.*.php> allow from all </Files> carve-out, so the file is fetched and executed by any unauthenticated visitor. This vulnerability is fixed in 6.7.3.

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

CubeCart versions before 6.7.3 allow an admin with documents edit permission to inject arbitrary PHP code into the Invoice Editor. When any admin prints an order, this template is written to a predictable PHP file in the files/ directory. The included .htaccess explicitly allows access to these print PHP files, enabling unauthenticated remote code execution.

MitigationUpgrade to CubeCart 6.7.3 or later immediately. Additionally, audit the files/ directory for any unexpected print.*.php files and remove them, and review admin permissions to limit who has documents edit access.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 installed CubeCart version
    Locate the version file or database entry. Common locations include: a version.php file in the root or admin/includes/ directory, or check the database for a version setting. Compare the found version to the affected range (before 6.7.3).
    Affected if The installed version is lower than 6.7.3
  2. Check for admin users with documents edit permission
    Access the admin panel and review user permissions, or query the database admin_user table for permission flags. Specifically look for users granted 'documents' or 'documents_edit' access rights.
    Affected if Any admin account has documents edit permission enabled
  3. Inspect files directory for suspicious PHP files
    Browse to the files/ directory (or files/sources/ depending on installation) and list all PHP files. Look for files matching patterns like print*.php, invoice*.php, or order*.php that were not created by the administrator.
    Affected if Unexpected print*.php or similar template files exist in the files/ directory
  4. Verify htaccess allows PHP execution in files directory
    Locate and read the .htaccess file inside the files/ directory. Check if it contains directives that permit execution of PHP scripts (such as SetHandler or AddType for PHP), which would allow unauthenticated access to any injected PHP files.
    Affected if The .htaccess in files/ explicitly allows PHP script execution

You are affected if your CubeCart installation is version 6.7.2 or lower AND an admin with documents edit permission exists, or if you find unexpected print PHP files in the files/ directory with PHP execution enabled via htaccess.

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 to CubeCart 6.7.3 or later immediately. Additionally, audit the files/ directory for any unexpected print.*.php files and remove them, and review admin permissions to limit who has documents edit access.

Recommended fix High confidence

CubeCart 6.7.3

  1. Backup the CubeCart installation and database before proceeding with any changes
  2. Download CubeCart version 6.7.3 from the official source (github.com or cubecart.com)
  3. Replace the existing CubeCart files with the new version 6.7.3 files, preserving configuration and custom assets
  4. Run any available database migration scripts included in the 6.7.3 release
  5. Log in as an administrator and verify the Invoice Editor no longer allows saving raw PHP code
  6. Test the order Print functionality to confirm templates render correctly without code injection
  7. Verify the fix by attempting to inject <?php phpinfo(); ?> into the Invoice Editor as an admin with documents edit permission - it should be sanitized or blocked
  8. Clear any application caches after upgrade
Caveat Review CubeCart 6.7.3 release notes for any breaking changes or deprecated features before upgrading production

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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