dbcve.org
BrillianceWordPress extension · Wpchill

CVE-2023-28171

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 1.3.1 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
Auth. (subscriber+) Stored Cross-Site Scripting (XSS) vulnerability in WP Chill Brilliance theme <= 1.3.1 versions.

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

A stored cross-site scripting (XSS) vulnerability exists in the WP Chill Brilliance WordPress theme versions 1.3.1 and below. The vulnerability can be exploited by authenticated users with subscriber-level privileges, allowing malicious JavaScript to be persistently embedded in content and executed when viewed by other users.

MitigationUpdate the WP Chill Brilliance theme to a version newer than 1.3.1 to receive the security patch that properly sanitizes user input.

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
BrillianceWordPress extension
Affected:<= 1.3.1

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. Identify if WP Chill Brilliance theme is installed
    Navigate to Appearance > Themes in WordPress admin panel, or inspect wp-content/themes/ directory for a folder named 'brilliance' or 'brilliance-child'.
    Affected if The Brilliance theme (or child theme) is active or installed on the WordPress site.
  2. Check installed theme version
    Access the theme's style.css file in wp-content/themes/brilliance/ and locate the 'Version:' header in the file comments, or view the theme details in WordPress admin under Appearance > Themes.
    Affected if The version number displayed is 1.3.1 or lower.
  3. Verify subscriber-level user access exists
    Navigate to Users > All Users in WordPress admin and review the list of users. Check if any users have the 'Subscriber' role assigned by viewing the role column.
    Affected if There is at least one user with Subscriber role, as this role can exploit the vulnerability.
  4. Inspect user-generated content for unsanitized scripts
    Review posts and pages created by subscriber-level users (check Posts > All Posts and filter by author). Look for script tags, event handlers (onload, onerror, onclick), or javascript: URIs in title, content, or custom fields.
    Affected if Content contains unescaped HTML script tags or JavaScript event handlers that would execute when viewed.
  5. Check theme files for missing sanitization
    If you have file access, review the theme's template files that handle subscriber content (such as single.php, content.php, or functions.php) for output functions that lack escaping functions like esc_html(), esc_attr(), or wp_kses().
    Affected if Theme code outputs user content without proper sanitization functions.

A site is affected if it runs WP Chill Brilliance theme version 1.3.1 or below AND allows subscriber-level users to post or edit content on the site.

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 a release after 1.3.1
Interim mitigation

Update the WP Chill Brilliance theme to a version newer than 1.3.1 to receive the security patch that properly sanitizes user input.

Recommended fix Moderate confidence

Latest available version of Brilliance theme (check WordPress theme repository or vendor for current release)

  1. Check WordPress admin panel under Appearance > Themes for the currently installed Brilliance theme version
  2. Navigate to the official WordPress theme repository or WP Chill website to download the latest version of the Brilliance theme
  3. Before updating, create a full backup of the WordPress site including database and files
  4. Update the Brilliance theme to the latest available version through WordPress admin or via FTP upload
  5. Verify the update was successful and check that the new version is >= 1.3.2
Caveat Review theme changelog for any template changes that may affect child theme customizations

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

Fix this in Brilliance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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