CVE-2013-3491
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in the Sharebar plugin 1.2.5 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) add or (2) modify buttons, or (3) insert cross-site scripting (XSS) sequences.
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 confidenceCSRF vulnerabilities in WordPress Sharebar plugin 1.2.5 allow remote attackers to trick administrators into unknowingly submitting requests that add or modify buttons, or inject XSS sequences, by leveraging the absence of anti-CSRF tokens or referer validation in the affected forms.
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.2.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Sharebar plugin installationIn your WordPress installation, navigate to wp-content/plugins/ and look for a folder named 'sharebar'. Check the main plugin file (usually sharebar.php) for the version declaration, or check the plugin metadata in WordPress admin under Plugins > Installed Plugins.Affected if The Sharebar plugin is installed and shows version 1.2.5
-
Verify the exact version numberOpen the main Sharebar plugin file and locate the version comment or variable (often labeled 'Version:', 'Version:', or '$version'). Compare this against the affected version 1.2.5.Affected if The installed version is exactly 1.2.5
-
Inspect admin forms for CSRF protectionAccess the Sharebar plugin settings page in WordPress admin (usually under Settings > Sharebar or a dedicated Sharebar admin menu). View the page source (right-click > View Page Source) and search for forms that handle button creation or modification.Affected if The admin forms for adding or modifying buttons lack 'wp_nonce_field' or '_wpnonce' hidden input fields
-
Check referer validation in plugin codeExamine the PHP file that handles the admin form submissions (typically the main sharebar.php or a separate admin handler file). Look for 'check_admin_referer' or 'wp_verify_nonce' function calls before processing form data.Affected if No referer validation (check_admin_referer) or nonce verification (wp_verify_nonce) is present in the form handling code
You are affected if the Sharebar plugin version 1.2.5 is installed and the admin forms for button management lack WordPress nonce tokens and referer validation.
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 dataImplement WordPress nonces and referer header validation on all admin action forms to prevent CSRF attacks; also apply proper input sanitization to prevent the XSS injection vector.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3491 — 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-2013-3491 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