AddonsWordPress extension · Themerex
CVE-2025-0682
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 · uneditedThe ThemeREX Addons plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.33.0 via the 'trx_sc_reviews' shortcode 'type' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.
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 confidenceThe ThemeREX Addons WordPress plugin before version 2.33.1 contains a Local File Inclusion vulnerability in the 'trx_sc_reviews' shortcode's 'type' attribute. Authenticated attackers with contributor-level or higher permissions can manipulate this parameter to include and execute arbitrary files on the server, leading to potential PHP code execution and complete site compromise.
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
< 2.34.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ThemeREX Addons versionIn WordPress admin, navigate to Plugins > Installed Plugins and locate ThemeREX Addons. Record the version number displayed. Alternatively, check the plugin header file (typically in /wp-content/plugins/trx-addons/) or use WP-CLI: wp plugin list --name="trx-addons"Affected if The installed version is lower than 2.34.0 (the summary indicates the fix was released in version 2.33.1, so versions prior to that are vulnerable)
-
Determine if contributor-level or higher users existIn WordPress admin, go to Users and review the role column for each account. Contributor, Author, Editor, and Administrator roles all meet the permission threshold for this attack. Check via WP-CLI: wp user list --role=contributorAffected if At least one user account with Contributor, Author, Editor, or Administrator role exists on the site
-
Detect trx_sc_reviews shortcode usageSearch WordPress database content for the shortcode. Use: wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%trx_sc_reviews%' AND post_status='publish'" or manually review published posts, pages, and widgets where this shortcode may be presentAffected if The trx_sc_reviews shortcode is actively used in any published content, enabling the attack surface
-
Inspect for signs of exploitation in uploads and logsReview /wp-content/uploads/ and other writable directories for unexpected .php files or modified files. Check server access and error logs (Apache error_log, nginx error.log) for patterns like 'trx_sc_reviews' combined with '../' path traversal sequences or attempts to include sensitive files such as /etc/passwd or wp-config.phpAffected if Suspicious PHP files exist in upload directories or logs show LFI attempts via the trx_sc_reviews shortcode parameter
A site is affected if it runs ThemeREX Addons versions before 2.34.0, has any authenticated user with contributor-level access, and uses the trx_sc_reviews shortcode, allowing a remote attacker to include and execute arbitrary files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.34.0
Update the ThemeREX Addons plugin to version 2.33.1 or later. Until patched, disable the plugin or restrict contributor-level user capabilities. Review uploaded files and server logs for signs of exploitation.
Version 2.34.0
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate ThemeREX Addons in the plugin list
- If an update is available, click 'Update Now' to upgrade to version 2.34.0 or later
- Alternatively, download version 2.34.0 from the ThemeREX provider and upload via Plugins > Add New > Upload Plugin
- After updating, verify the plugin version shows 2.34.0 or higher in the plugins list
- Consider reviewing user accounts with contributor-level and above permissions to ensure no malicious shortcodes were added during the vulnerability window
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Addons
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0682 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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