CVE-2021-20780
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 WPCS - WordPress Currency Switcher 1.1.6 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 confidenceCSRF vulnerability in the WPCS WordPress Currency Switcher plugin versions 1.1.6 and earlier allows remote attackers to hijack administrator authentication by tricking logged-in admins into submitting malicious requests, potentially leading to full 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<= 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
- 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.
-
Locate the WPCS WordPress Currency Switcher pluginAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WPCS WordPress Currency Switcher', 'Wp Currency Wordpress Currency Switcher', or similar currency switcher plugin names. Alternatively, check your web server filesystem at wp-content/plugins/ for the plugin directory.Affected if Plugin is present in the installation
-
Identify the installed plugin versionIn WordPress admin, click on the plugin name to view details and find the version number. Or via FTP/filesystem, open the plugin's main PHP file or readme.txt and locate the 'Version' header field.Affected if Version number cannot be determined or is not visible
-
Compare version against affected rangeCheck if the installed version is 1.1.6 or earlier. Version 1.1.7 and later include anti-CSRF token validation that remediates this issue.Affected if Installed version is 1.1.6 or lower
If the WPCS WordPress Currency Switcher plugin version is 1.1.6 or earlier, the environment is vulnerable to CVE-2021-20780 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 WPCS - WordPress Currency Switcher to version 1.1.7 or later which includes anti-CSRF token validation; as an interim measure, administrators should avoid clicking suspicious links while logged in.
WPCS - WordPress Currency Switcher version 1.1.7 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'WPCS - WordPress Currency Switcher' in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from wordpress.org or the vendor (pluginus.net) and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20780 — 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-20780 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