dbcve.org
BricksWordPress extension · Bricksbuilder

CVE-2023-3410

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-14
Fix available
A fix is available. Upgrade to 1.10.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Bricks theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘customTag' attribute in versions up to, and including, 1.10.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with access to the Bricks Builder (admin-only by default), to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This becomes more of an issue when Bricks Builder access is granted to lower-privileged users.

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 confidence

The Bricks WordPress theme versions up to 1.10.1 contain a stored Cross-Site Scripting vulnerability in the 'customTag' attribute. Due to insufficient input sanitization and output escaping, authenticated attackers with Bricks Builder access can inject arbitrary JavaScript that persists on pages and executes whenever users access those pages.

MitigationUpdate Bricks theme to version 1.10.2 or later to patch this vulnerability. Limit Bricks Builder access to trusted admin users only and audit existing pages for malicious customTag content.

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
BricksWordPress extension
Affected:< 1.10.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Bricks theme is installed and active
    Check WordPress dashboard under Appearance > Themes or examine wp-content/themes directory for the Bricks theme folder
    Affected if Bricks theme is present and activated on the WordPress site
  2. Determine installed Bricks version
    Navigate to Bricks > Settings > General in WordPress admin, or open the style.css file in the Bricks theme folder and locate the Version header
    Affected if Version number is below 1.10.2 (e.g., 1.10.1, 1.10.0, 1.9.x, etc.)
  3. Identify users with Bricks Builder access
    Check WordPress user roles and Bricks role settings under Bricks > Settings > Role Manager to see which users can access the builder editor
    Affected if Any untrusted or non-admin user accounts have Bricks Builder access enabled
  4. Scan for malicious customTag attribute values
    Use WordPress database query (e.g., via phpMyAdmin) to search post meta table for 'customTag' entries containing script tags, javascript:, or onload/onerror event handlers; alternatively, inspect rendered page HTML using browser developer tools
    Affected if Any page contains customTag attribute values with embedded JavaScript code

User is affected if Bricks theme version is below 1.10.2 AND the Bricks Builder is accessible to users who could inject malicious customTag content into pages.

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 1.10.2 or later
Fixed in 1.10.2
Interim mitigation

Update Bricks theme to version 1.10.2 or later to patch this vulnerability. Limit Bricks Builder access to trusted admin users only and audit existing pages for malicious customTag content.

Recommended fix High confidence

Bricks 1.10.2 or later

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. Locate the Bricks theme and check for an update to version 1.10.2 or later
  4. Update the Bricks theme to the latest available version (1.10.2 or higher)
  5. Verify the update was successful by checking the theme version
  6. Clear any caching plugins or server-side caches to ensure the patched code is served
  7. Review any pages using the customTag attribute to confirm the malicious scripts are no longer present

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

Fix this in Bricks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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