dbcve.org
Stockholm CoreWordPress extension · Select Themes

CVE-2024-34553

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 2.4.2 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Select-Themes Stockholm Core allows Reflected XSS.This issue affects Stockholm Core: from n/a through 2.4.1.

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

Reflected XSS vulnerability in Select-Themes Stockholm Core where user-supplied input is not properly sanitized or escaped before being rendered in web pages, allowing attackers to inject malicious JavaScript code that executes in the context of the victim's browser.

MitigationApply proper input validation and output encoding/escaping (e.g., using functions like esc_html(), esc_attr(), or wp_kses() in WordPress contexts) to all user-supplied data before rendering it in HTML, JavaScript, or URL contexts.

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
Stockholm CoreWordPress extension
Affected:< 2.4.2

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.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 checks

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

  1. Locate Stockholm Core theme files
    Check your WordPress installation under wp-content/themes/ or wp-content/themes/stockholm/ for the presence of the Stockholm theme files, particularly style.css or version.php that contains the theme version information.
    Affected if The Stockholm theme directory exists on the server.
  2. Determine installed version
    Open the theme's style.css file in the Stockholm theme folder and look for the 'Version:' declaration in the file header comment, or check version.php if it exists.
    Affected if The reported version number is less than 2.4.2 (e.g., 2.4.1, 2.4.0, 2.3.x, etc.).
  3. Identify input handling points
    Search the theme's PHP files (particularly in template files, header.php, or any files handling form inputs or URL parameters) for occurrences where user-supplied input like $_GET, $_POST, or request variables are output to HTML without sanitization functions such as esc_html(), esc_attr(), or wp_kses().
    Affected if The theme code outputs request parameters directly into HTML without proper escaping functions.
  4. Check WordPress version context
    Verify your WordPress core version by navigating to Dashboard > Updates or checking wp-includes/version.php, as some XSS mitigations may depend on WordPress core protections.
    Affected if WordPress core is outdated and lacks updated sanitization functions needed to protect against this XSS vector.

You are affected if the Stockholm Core theme version is installed and is lower than 2.4.2, and the theme handles user-supplied input that gets rendered in web pages without sanitization.

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.

dbcve · scoped
Upgrade available Upgrade to 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Apply proper input validation and output encoding/escaping (e.g., using functions like esc_html(), esc_attr(), or wp_kses() in WordPress contexts) to all user-supplied data before rendering it in HTML, JavaScript, or URL contexts.

Recommended fix Moderate confidence

Stockholm Core version 2.4.2

  1. Backup your current website files and database before making any changes
  2. Update Stockholm Core theme to version 2.4.2 or later through WordPress admin dashboard (Appearance > Themes) or via FTP upload of the new version
  3. Verify the update was successful by checking the theme version in WordPress admin
  4. Clear any caching plugins or server-side caches after the update
  5. Test the affected functionality to confirm the XSS vulnerability is resolved
  6. Monitor for any plugin/theme compatibility issues after the update
Caveat Minor theme update - review changelog for any template or functionality changes that may require adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Stockholm Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34553 — 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-2024-34553 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