dbcve.org
Builder Theme DepotWordPress extension · Ithemes

CVE-2015-9377

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-28
Fix available
A fix is available. Upgrade to 5.0.30 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
iThemes Builder Theme Depot before 5.0.30 for WordPress has XSS via add_query_arg() and remove_query_arg().

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 confidence

Cross-site scripting (XSS) vulnerability in iThemes Builder Theme Depot plugin/theme for WordPress. The issue stems from improper use of add_query_arg() and remove_query_arg() functions, which fail to sanitize URL parameters before outputting them, allowing injection of malicious scripts via crafted URLs.

MitigationUpdate iThemes Builder Theme Depot to version 5.0.30 or later, which contains the fix for proper URL parameter escaping.

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
Builder Theme DepotWordPress extension
Affected:< 5.0.30

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iThemes Builder Theme Depot version
    Navigate to WordPress admin > Appearance > Themes (or Plugins) and locate Builder Theme Depot. The version is displayed in the theme/plugin details. Alternatively, inspect the main theme/plugin file header (usually style.css for themes or the main plugin PHP file) for the 'Version' field.
    Affected if Version is displayed as lower than 5.0.30 (e.g., 5.0.20, 5.0.0, etc.) or the Version field is missing entirely.
  2. Verify the theme/plugin is active
    In WordPress admin, go to Appearance > Themes (or Plugins) and confirm that Builder Theme Depot is currently activated. For plugins, check that the iThemes Builder plugin is active.
    Affected if The theme or plugin is installed and actively in use on the WordPress site.
  3. Identify use of query arg functions in theme files
    Search the theme/plugin files for instances of 'add_query_arg' and 'remove_query_arg'. Common locations include header.php, footer.php, template files, and shortcode handlers. Use grep or a code editor to search the /wp-content/themes/builder-theme-depot/ directory.
    Affected if These functions are found and the returned value is directly output to HTML (echoed) without subsequent sanitization using functions like esc_url(), esc_attr(), or htmlspecialchars().
  4. Inspect rendered pages for unsanitized URLs
    Visit pages on the site, right-click and view page source. Look for URLs in links, form actions, or redirects that contain the site's own query parameters. Check if these URLs are properly escaped in the HTML output.
    Affected if Query parameters in rendered URLs appear unescaped or contain characters that should have been sanitized (e.g., unescaped ampersands in href attributes).

A user is affected if iThemes Builder Theme Depot version is below 5.0.30 AND the theme/plugin is active, with query arg functions being used in a way that outputs URLs without proper escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.0.30 or later
Fixed in 5.0.30
Interim mitigation

Update iThemes Builder Theme Depot to version 5.0.30 or later, which contains the fix for proper URL parameter escaping.

Fix this in Builder Theme Depot Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9377 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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