CVE-2013-3638
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 · uneditedSQL injection vulnerability in Boonex Dolphin before 7.1.3 allows remote authenticated users to execute arbitrary SQL commands via the 'pathes' parameter in 'categories.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 · high confidenceSQL injection vulnerability in Boonex Dolphin CMS before version 7.1.3 allows authenticated remote attackers to execute arbitrary SQL commands through the 'pathes' parameter in categories.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate SQL queries.
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< 7.1.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Boonex Dolphin installationLook for Boonex Dolphin CMS files in your web root directory, typically in a folder named 'dolphin' or check for the presence of typical Dolphin files like 'inc/header.php' or 'administration/index.php'Affected if Boonex Dolphin CMS is present on the server
-
Identify installed Dolphin versionCheck the version file or footer/admin panel for the Dolphin version number. Common locations include a version.php file or the admin dashboard under System Info or Site InfoAffected if The installed version is less than 7.1.3 (e.g., 7.1.2, 7.1.1, 7.0.x, etc.)
-
Locate categories.php fileSearch the web directory for categories.php - typically found in the root Dolphin folder or in a modules/categories directoryAffected if The categories.php file exists in the Dolphin installation
-
Check if pathes parameter is processedExamine the categories.php file for code handling the 'pathes' parameter, specifically looking for direct use in SQL queries without visible sanitization or parameterized query usageAffected if The 'pathes' parameter is used in SQL queries without prepared statements or proper escaping
-
Verify authentication requirementsDetermine if the vulnerable endpoint requires authentication by testing access to categories.php or reviewing the authentication logic in the fileAffected if An authenticated user account can access categories.php with the 'pathes' parameter
You are affected if Boonex Dolphin CMS version is below 7.1.3 and the categories.php file with the vulnerable 'pathes' parameter is accessible to authenticated users.
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 data7.1.3
Upgrade to Boonex Dolphin 7.1.3 or later to obtain the vendor patch. Alternatively, implement parameterized queries or proper input validation on the 'pathes' parameter in categories.php to remediate the injection point.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3638 — 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-2013-3638 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