dbcve.org
Cash Point \& Transport OptimizerApplication · Sesami

CVE-2023-31294

HIGH · 7.5 CVSS v3.1 Published 2023-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
CSV Injection vulnerability in Sesami Cash Point & Transport Optimizer (CPTO) version 6.3.8.6 (#718), allows remote attackers to obtain sensitive information via the Delivery Name field.

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

A CSV Injection vulnerability exists in Sesami CPTO version 6.3.8.6 where the Delivery Name field does not properly sanitize user input before exporting to CSV files. Attackers can embed spreadsheet formulas (e.g., =CMD|' /C calc'!A0) into the Delivery Name field; when the exported CSV is opened in spreadsheet software, these formulas execute, allowing sensitive data exfiltration via HTTP/DNS requests or command execution.

MitigationImplement strict input validation on the Delivery Name field to reject formula characters (=, +, -, @) and encode/sanitize all CSV export outputs to prevent formula injection.

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
Cash Point \& Transport OptimizerApplication
Affected:= 6.3.8.6.718

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify the installed Sesami CPTO version
    Access the application's About or Version information panel, or check the application executable/properties for the build number. Look for version 6.3.8.6.718 specifically.
    Affected if The installed version is 6.3.8.6.718 exactly, as this is the only confirmed affected version.
  2. Determine if Delivery Name field is in use
    Navigate to the shipment/delivery creation or edit interface in the application and locate the Delivery Name input field. Check if the field accepts user input and if any existing delivery records contain data in this field.
    Affected if The Delivery Name field exists and is accessible for input, indicating the vulnerable feature is present.
  3. Verify CSV export functionality exists
    Locate the export or reporting feature in the application menu. Look for options to export delivery/shipment data to CSV format, typically found under Export, Reports, or Data Transfer menus.
    Affected if CSV export functionality is present and accessible to users who can create or modify Delivery Name entries.
  4. Inspect Delivery Name input handling
    Submit a test delivery with a Delivery Name containing formula characters (=, +, -, @) and observe if the application rejects or sanitizes these characters before saving. Check application logs for any validation warnings.
    Affected if The application accepts formula characters (=, +, -, @) in the Delivery Name field without sanitization or rejection.
  5. Review CSV export output for sanitization
    Export delivery data to CSV and open the resulting file in a text editor. Examine the Delivery Name field content to see if formula characters are encoded (e.g., = becomes '= or = replaced with empty/space).
    Affected if The exported CSV contains raw formula characters (=, +, -, @) in the Delivery Name field without encoding or escaping.

A user is affected if they have Sesami CPTO version 6.3.8.6.718 installed, use the Delivery Name field, have access to CSV export, and the application does not sanitize formula characters in the Delivery Name field before CSV export.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the Delivery Name field to reject formula characters (=, +, -, @) and encode/sanitize all CSV export outputs to prevent formula injection.

Fix this in Cash Point \& Transport Optimizer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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