Royal Elementor AddonsWordPress extension
CVE-2022-47175
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in P Royal Royal Elementor Addons and Templates plugin <= 1.3.75 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Royal Elementor Addons and Templates WordPress plugin versions 1.3.75 and below allows attackers to trick authenticated users into performing unintended actions by forcing their browser to send malicious requests.
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
Royal Elementor AddonsWordPress extension
<= 1.3.75CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if Royal Elementor Addons plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Elementor Addons' or check the plugin files via FTP at wp-content/plugins/royal-elementor-addons/Affected if The plugin is installed and active on the WordPress site
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins, find Royal Elementor Addons, and check the version number displayed under the plugin name. Alternatively, read the main plugin file header at wp-content/plugins/royal-elementor-addons/royal-elementor-addons.php and look for 'Version:'Affected if The version number is 1.3.75 or lower
-
Confirm vulnerability scopeThis is a CSRF vulnerability affecting state-changing operations. The vulnerability requires an authenticated user with administrator-level privileges to be tricked into clicking a malicious link while logged in. Review plugin settings and form submissions to see if they include proper nonce validation.Affected if The installed version is 1.3.75 or lower and no external anti-CSRF measures have been manually added to the site
The site is affected if Royal Elementor Addons plugin version 1.3.75 or lower is installed and active, allowing authenticated administrators to be exploited via CSRF attacks.
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 · scopedUpdate the Royal Elementor Addons and Templates plugin to the latest version, which should include proper anti-CSRF token validation (nonces) for state-changing operations.
Latest version of Royal Elementor Addons (greater than 1.3.75)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'Royal Elementor Addons' in the plugin list
- Check if an update is available and install the latest version
- Verify the updated version number is greater than 1.3.75
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Royal Elementor Addons
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47175 — 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-2022-47175 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