CVE-2007-5364
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 · uneditedDirectory traversal vulnerability in payments/ideal_process.php in the iDEAL transaction handler in ViArt Shopping Cart allows remote attackers to have an unknown impact via directory traversal sequences in the filename parameter to the createCertFingerprint function. NOTE: this issue is disputed by CVE because PHP encounters a fatal function-call error on a direct request for payments/ideal_process.php
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 confidenceDirectory traversal vulnerability in payments/ideal_process.php in ViArt Shopping Cart allows manipulation of the filename parameter in the createCertFingerprint function. However, CVE notes this is disputed because PHP encounters a fatal function-call error on direct request, making actual exploitation uncertain.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Locate the vulnerable fileFind the payments/ideal_process.php file in your ViArt Shopping Cart installation directory. Common paths include /payments/ideal_process.php or /shop/payments/ideal_process.php relative to the web root.Affected if The file exists in the installation
-
Verify iDEAL payment handler is configuredCheck your ViArt admin panel for iDEAL payment module settings, or search configuration files for 'ideal' or 'iDEAL' references to confirm this payment handler is enabled.Affected if iDEAL payment processing is active or has been configured
-
Examine the createCertFingerprint functionOpen payments/ideal_process.php in a text editor and locate the createCertFingerprint function. Look for usage of the 'filename' parameter without proper sanitization, particularly code that passes this parameter to file operations like fopen, file_get_contents, or include/require.Affected if The function uses the filename parameter in file operations without input validation
-
Confirm ViArt Shopping Cart installationCheck your installation for ViArt Shopping Cart files. Look for version indicators in files like version.php, or check the admin dashboard for the installed version number.Affected if ViArt Shopping Cart software is installed (all versions are affected)
You are affected if ViArt Shopping Cart is installed, the payments/ideal_process.php file exists, and the iDEAL payment handler is or was enabled.
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 dataEvaluate whether the payments/ideal_process.php file is necessary; if so, apply vendor patches or implement strict input validation on the filename parameter to prevent directory traversal. Consider disabling the iDEAL transaction handler if unused.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5364 — 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-2007-5364 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