SharebarWordPress extension · Sharebar Project
CVE-2012-6719
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 sharebar plugin before 1.2.2 for WordPress has SQL injection.
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 confidenceSQL injection vulnerability in the sharebar WordPress plugin affecting versions prior to 1.2.2, allowing remote attackers to execute arbitrary SQL queries through unsanitized user input.
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
< 1.2.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 Sharebar plugin is installedInspect the WordPress plugins directory at wp-content/plugins/ for a sharebar folder, or check the WordPress admin under Plugins > Installed Plugins for an entry named 'Sharebar' or 'Sharebar Project Sharebar'Affected if The sharebar plugin folder exists in wp-content/plugins/ or appears in the WordPress plugins list
-
Determine the installed Sharebar versionOpen the main Sharebar plugin file (typically sharebar.php) in a text editor or via file manager, then locate the version comment or Version: header in the plugin file headerAffected if The version number displayed is less than 1.2.2 (for example 1.2.1, 1.2.0, 1.1.x, or any version before 1.2.2)
-
Verify the SQL injection attack surface existsExamine the Sharebar plugin source code for database query functions (such as $wpdb->prepare, mysql_query, or direct query concatenation) that handle user input without sanitization, particularly parameters that accept user-supplied valuesAffected if User input (GET, POST, or cookie parameters) is used directly in SQL queries without prepared statements or escaping functions
A system is affected if the Sharebar plugin version is installed and is lower than 1.2.2, exposing unsanitized user input to SQL query functions.
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 · scoped1.2.2
Update the sharebar plugin to version 1.2.2 or later to remediate the SQL injection vulnerability.
Sharebar version 1.2.2
- Backup your WordPress database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate the Sharebar plugin and click 'Update Now' if an update is available, or reinstall version 1.2.2
- Alternatively, use WP-CLI: wp plugin install sharebar --version=1.2.2 --force
- Verify the plugin version is now 1.2.2 in the Plugins list
- Test that the plugin functionality works correctly after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Sharebar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6719 — 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-2012-6719 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