dbcve.org
SharebarWordPress extension · Sharebar Project

CVE-2012-6718

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-28
Fix available
A fix is available. Upgrade to 1.2.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The sharebar plugin before 1.2.2 for WordPress has XSS, a different issue than CVE-2013-3491.

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 confidence

The sharebar WordPress plugin before version 1.2.2 contains a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages served by the plugin.

MitigationUpdate the sharebar plugin to version 1.2.2 or later to remediate the XSS vulnerability.

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
SharebarWordPress extension
Affected:< 1.2.2

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the sharebar plugin directory
    Access your WordPress installation via FTP or file manager, navigate to /wp-content/plugins/ and identify the sharebar folder
    Affected if The sharebar folder exists in the plugins directory
  2. Find the plugin version file
    Within the sharebar plugin folder, open the main PHP file (usually sharebar.php or similar) and look for the plugin header comment containing 'Version: x.x.x'
    Affected if The version number displayed is lower than 1.2.2 (for example, 1.2.1, 1.2.0, or earlier)
  3. Check WordPress plugin admin interface
    Log into WordPress admin panel, go to Plugins > Installed Plugins, find 'Sharebar' or 'Sharebar Project Sharebar' in the list and note the version displayed under the plugin name
    Affected if The version shown is less than 1.2.2

You are affected if the sharebar plugin is installed and its version is below 1.2.2, as this is where the XSS vulnerability exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.2.2 or later
Fixed in 1.2.2
Interim mitigation

Update the sharebar plugin to version 1.2.2 or later to remediate the XSS vulnerability.

Fix this in Sharebar Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-6718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-6718 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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