Rife Elementor Extensions \& TemplatesWordPress extension · Apollo13themes
CVE-2021-24265
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 “Rife Elementor Extensions & Templates” WordPress Plugin before 1.1.6 has a widget that is vulnerable to stored Cross-Site Scripting(XSS) by lower-privileged users such as contributors, all via a similar method.
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 confidenceThe Rife Elementor Extensions & Templates WordPress plugin before version 1.1.6 contains a stored Cross-Site Scripting (XSS) vulnerability in one of its widgets. Lower-privileged users such as contributors can inject malicious JavaScript code through the widget's input fields, which is then stored and executed when other users view the affected 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
Rife Elementor Extensions \& TemplatesWordPress extension
< 1.1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'Rife Elementor Extensions & Templates' and note the version number displayedAffected if version number is less than 1.1.6
-
Identify if the vulnerable widget is in useReview all pages and posts created with Elementor, looking for widgets added by the Rife Elementor Extensions plugin. Check the widget panel for any 'Rife' or 'Apollo13themes' branded widgetsAffected if any Rife/Apollo13themes widgets are present on published content
-
Inspect widget input fields for injected scriptsEdit each page/post containing the Rife widget, open the widget settings, and examine all text input fields, particularly any that accept user-generated content or allow HTML/script inputAffected if any input fields contain script tags, event handlers (onclick, onload, etc.), or suspicious JavaScript code
-
Examine stored content in the databaseQuery the WordPress database tables (wp_posts, wp_postmeta) for entries containing the Rife widget and look for encoded or raw script tags within post contentAffected if database records show script tags or malicious JavaScript within widget content
-
Verify if lower-privileged users have access to the widgetCheck user role capabilities: go to Users > All Users and review roles (Contributor, Author, Editor) that can access the Elementor editor with the Rife widget availableAffected if Contributor or Author roles can access and edit pages containing the vulnerable widget
You are affected if the Rife Elementor Extensions & Templates plugin version is below 1.1.6 and the vulnerable widget is in use with injected malicious scripts stored in your content.
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.
From vendor data1.1.6
Update the Rife Elementor Extensions & Templates plugin to version 1.1.6 or later to patch the stored XSS vulnerability. Review existing content for any injected malicious scripts.
Fix this in Rife Elementor Extensions \& Templates
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24265 — 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-2021-24265 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