Custom SidebarsWordPress extension · Wpmudev
CVE-2017-18510
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 custom-sidebars plugin before 3.1.0 for WordPress has CSRF related to set location, import actions, and export actions.
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 custom-sidebars WordPress plugin before version 3.1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability affecting its set location, import, and export functionality. The plugin fails to properly validate CSRF tokens on these actions, allowing attackers to trick authenticated administrators into unknowingly performing these operations through maliciously crafted 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
Custom SidebarsWordPress extension
< 3.1.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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.
-
Verify Custom Sidebars plugin is installedNavigate to WordPress admin > Plugins and look for 'Custom Sidebars' by WPMU DEV in the installed plugins listAffected if Plugin is not found in the plugins list - not vulnerable
-
Check the installed plugin versionIn WordPress admin > Plugins, click on the Custom Sidebars plugin to view its details, or check the plugin files in /wp-content/plugins/custom-sidebars/ for a version indicatorAffected if Version displayed is less than 3.1.0 or no version is shown and the plugin appears old
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the Custom Sidebars plugin shows as 'Active'Affected if Plugin is active - the vulnerable code can be executed; if inactive, the vulnerability cannot be exploited
-
Check for administrator user sessionsIn WordPress admin > Users, confirm there are users with Administrator role currently active or able to access the admin areaAffected if Administrators have active sessions - CSRF attacks require tricking a logged-in administrator
-
Verify access to vulnerable features existsNavigate to the Custom Sidebars settings area (typically under Appearance > Custom Sidebars) and confirm the Set Location, Import, or Export options are present and accessibleAffected if Any of these three features (set location, import, export) are available and accessible to administrators
The environment is affected if the Custom Sidebars plugin version is below 3.1.0, the plugin is active, and administrators can access the set location, import, or export functionality.
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 data3.1.0
Update the custom-sidebars plugin to version 3.1.0 or later, which includes proper CSRF token validation. Until updated, administrators should avoid clicking untrusted links while logged into WordPress admin areas.
Fix this in Custom Sidebars
Scoped from the published advisory
- 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-2017-18510 — 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-2017-18510 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