CVE-2023-31295
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 · uneditedCSV Injection vulnerability in Sesami Cash Point & Transport Optimizer (CPTO) version 6.3.8.6 (#718), allows remote attackers to obtain sensitive information via the User Profile 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 · moderate confidenceCSV Injection vulnerability in Sesami CPTO version 6.3.8.6 allows remote attackers to inject malicious formulas into the User Profile field. When exported as CSV and opened in spreadsheet software, these formulas can be executed to exfiltrate sensitive system information.
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= 6.3.8.6.718CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Sesami CPTO versionLocate the installed version of Sesami Cash Point & Transport Optimizer through the application's About panel, version info in the executable properties, or installation directory metadata. Compare the exact version string to 6.3.8.6.718.Affected if The installed version is 6.3.8.6.718 or falls within the affected release build.
-
Confirm User Profile feature is accessibleLog into Sesami CPTO and navigate to the User Profile settings or administration panel where end users can view and edit their profile information.Affected if The User Profile field is available and editable by users or administrators.
-
Identify CSV export functionalityLocate any export, data dump, or reporting feature within Sesami CPTO that allows exporting user data including User Profile fields to CSV format.Affected if CSV export capability exists and includes User Profile data in the output.
-
Test User Profile for input validationAttempt to insert special characters (=, +, -, @, tab, carriage return) into the User Profile field and then export to CSV. Inspect the raw CSV file to see if these characters are present without encoding or sanitization.Affected if The User Profile field accepts special characters without sanitization and the CSV output contains unencoded formula characters.
You are affected if you are running Sesami CPTO version 6.3.8.6.718 and have the User Profile feature enabled with CSV export capability that does not sanitize or encode formula characters.
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.
From vendor dataImplement strict input validation on the User Profile field to sanitize or reject special characters used in formula injection (e.g., =, +, -, @, tab, carriage return). Additionally, apply output encoding when generating CSV files to prevent formula execution.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-31295 — 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-2023-31295 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