CVE-2015-4129
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 Subrion CMS before 3.3.3 allows remote authenticated users to execute arbitrary SQL commands via modified serialized data in a salt cookie.
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 confidenceSQL injection vulnerability in Subrion CMS versions prior to 3.3.3 allows remote authenticated users to execute arbitrary SQL commands via manipulation of serialized data in a salt cookie. The unsanitized cookie value is directly used in SQL query construction.
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<= 3.3.2CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Identify Subrion CMS installationCheck for Subrion CMS files by looking for the typical installation directory structure, or search for known Subrion files like 'index.php' with Subrion branding in the HTML source or footer.Affected if Subrion CMS is present on the server.
-
Determine the installed Subrion versionLocate the version file or configuration. Common paths include checking the main index.php for a version constant, or looking in an 'includes' or 'config' directory for a version-defining file. Compare the found version against 3.3.3.Affected if The installed version is 3.3.2 or earlier.
-
Verify the salt cookie mechanism is activeExamine the authentication-related code files, typically found in the 'includes' or 'classes' directories, for the 'salt' cookie handling logic. The vulnerability lies in how the salt cookie value is processed during authentication checks.Affected if The salt cookie handling code exists and processes cookie values without proper sanitization in SQL queries.
-
Confirm user authentication is possibleDetermine if user registration or admin access is enabled on the site. The SQL injection requires a remote authenticated user, meaning any valid user account (including potentially a newly registered one) can exploit this flaw.Affected if User accounts can be created or existing user credentials are available for login.
The environment is affected if Subrion CMS version 3.3.2 or earlier is installed with the salt cookie authentication mechanism enabled and 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 dataUpgrade Subrion CMS to version 3.3.3 or later which contains the patch for this SQL injection vulnerability.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4129 — 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-2015-4129 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