Boot StoreWordPress extension · Thecartpress
CVE-2015-4582
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 · uneditedThe TheCartPress boot-store (aka Boot Store) theme 1.6.4 for WordPress allows header.php tcp_register_error XSS. NOTE: CVE-2015-4582 is not assigned to any Oracle product.
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 confidenceThe TheCartPress boot-store theme version 1.6.4 for WordPress contains a cross-site scripting (XSS) vulnerability in the header.php file. The vulnerability stems from improper sanitization of the tcp_register_error parameter, allowing attackers to inject malicious JavaScript code that executes in the browsers of users viewing affected pages.
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
Boot StoreWordPress extension
= 1.6.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 TheCartPress boot-store theme is installedNavigate to WordPress wp-content/themes directory and look for a folder named 'boot-store' or check via WordPress admin under Appearance > ThemesAffected if The boot-store theme is present in the WordPress installation
-
Check the installed theme versionOpen the style.css file in the boot-store theme folder and locate the 'Version:' comment in the file headerAffected if The version listed is exactly 1.6.4
-
Locate the vulnerable header.php fileNavigate to the boot-store theme folder and find header.phpAffected if The file header.php exists in the boot-store theme directory
-
Inspect header.php for tcp_register_error usageOpen header.php and search for occurrences of 'tcp_register_error' - look for code that retrieves this parameter (such as $_GET['tcp_register_error'] or similar) and outputs it to the pageAffected if The file contains code that uses the tcp_register_error parameter without sanitization functions like esc_html(), esc_attr(), or htmlspecialchars()
-
Check if user registration feature is enabledIn WordPress admin, go to Settings > General and verify if 'Anyone can register' is enabled, as this parameter relates to registration errorsAffected if User registration is enabled and the vulnerable theme version 1.6.4 is installed
A user is affected if the TheCartPress boot-store theme version 1.6.4 is installed AND header.php contains unsanitized output of the tcp_register_error parameter.
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 dataUpdate the TheCartPress boot-store theme to the latest patched version, or implement proper input sanitization/encoding for the tcp_register_error parameter in header.php before rendering.
Fix this in Boot Store
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4582 — 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-4582 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