dbcve.org
AddonsWordPress extension · Themerex

CVE-2025-6997

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-19
Fix available
A fix is available. Upgrade to 2.35.2.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 ThemeREX Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 2.35.1.1 due to insufficient input sanitization and output escaping. The plugin’s SVG rendering routine calls the trx_addons_get_svg_from_file() function on an unvalidated 'svg' parameter supplied via the shortcode or Elementor widget settings, then outputs it via the trx_addons_show_layout() function. Because there is no check on the URL’s origin, scheme, or the SVG content itself, authenticated attackers, with Contributor-level access and above, can supply a remote SVG and inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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 ThemeREX Addons WordPress plugin has a stored XSS vulnerability in its SVG rendering. The trx_addons_get_svg_from_file() function processes an unvalidated 'svg' parameter from shortcodes or Elementor widgets without checking URL origin, scheme, or SVG content, and trx_addons_show_layout() outputs it without proper escaping, allowing authenticated Contributor+ users to inject malicious scripts via SVG files.

MitigationUpdate to version 2.35.2 or later; alternatively, implement proper input validation for the svg parameter including URL origin/scheme validation and SVG content sanitization before rendering.

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
AddonsWordPress extension
Affected:< 2.35.2.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 ThemeREX Addons plugin is installed
    Navigate to WordPress admin > Plugins and look for 'ThemeREX Addons' in the installed plugins list, or query the wp_plugins database table for the plugin slug containing 'trx-addons'
    Affected if The plugin is present on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the ThemeREX Addons plugin to view its version number, or inspect the plugin main file header for the 'Version' tag
    Affected if The installed version is earlier than 2.35.2.2 (e.g., 2.35.1, 2.30.5, etc.)
  3. Determine if SVG shortcodes or widgets are in use
    Search WordPress post/content database for occurrences of the 'svg' parameter in shortcodes (e.g., [trx_addons_sc_skills svg="..."] or similar) or check Elementor pages for widgets that include SVG file references
    Affected if SVG-related shortcodes or Elementor widgets containing a 'svg' parameter are actively used on the site
  4. Inspect SVG file handling configuration
    Review the theme or plugin settings pages in WordPress admin for any SVG upload or display functionality that may be enabled, and examine the trx_addons_get_svg_from_file() function behavior if accessible in the codebase
    Affected if SVG file rendering from external or uploaded sources is enabled and the function processes the 'svg' parameter without validation
  5. Check for suspicious stored content in posts/pages
    Query the wp_posts database table for any posts containing '<script', 'javascript:', or SVG-related markup in the post_content field, particularly in fields corresponding to the 'svg' parameter
    Affected if Malicious script tags or event handlers are found stored in post content

A site is affected if it runs ThemeREX Addons version before 2.35.2.2 AND uses the SVG rendering feature via shortcodes or Elementor widgets with an unvalidated 'svg' parameter.

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.35.2.2 or later
Fixed in 2.35.2.2
Interim mitigation

Update to version 2.35.2 or later; alternatively, implement proper input validation for the svg parameter including URL origin/scheme validation and SVG content sanitization before rendering.

Recommended fix High confidence

2.35.2.2

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find ThemeREX Addons in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 2.35.2.2
  5. Alternatively, manually upload ThemeREX Addons version 2.35.2.2 via Plugins > Add New > Upload Plugin
  6. Verify the plugin version shows 2.35.2.2 after updating
  7. Test the SVG rendering functionality to ensure the fix does not break legitimate SVG usage

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

Fix this in Addons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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