dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7659

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Advanced Social Media Icons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `social` shortcode in all versions up to, and including, 1.2. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Advanced Social Media Icons WordPress plugin versions 1.2 and below contain a stored XSS vulnerability in the 'social' shortcode. Attackers with Contributor-level permissions can inject malicious JavaScript through unsanitized shortcode attributes; the payload persists in the database and executes whenever users view pages containing the shortcode.

MitigationImplement proper input sanitization using WordPress sanitization functions (such as sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr, esc_js) for all user-supplied shortcode attributes before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify plugin installation and version
    Navigate to WordPress Admin > Plugins > Installed Plugins. Look for 'Advanced Social Media Icons' and note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The installed version is 1.2 or lower, or the version field is missing or unreadable.
  2. Locate pages using the social shortcode
    Use WordPress search or a database query to find posts, pages, or custom post types containing the shortcode pattern '[social' or '[social_icons'. Check the post content in the wp_posts table or via the WordPress admin search.
    Affected if Any post, page, or custom post type contains a [social] or [social_icons] shortcode.
  3. Inspect shortcode attribute values in content
    Examine the content of posts containing the shortcode. Look for any attribute values that may contain unescaped characters such as quotes, angle brackets, or JavaScript event handlers. View the raw post content in the database or use a plugin to inspect stored shortcode data.
    Affected if Shortcode attributes contain raw or unsanitized values, especially if they include quotes, apostrophes, or characters that could be interpreted as HTML or JavaScript.
  4. Verify contributor-level user access
    Go to WordPress Admin > Users > Roles and Permissions. Check if the Contributor role exists and has access to create or edit posts where shortcodes can be inserted. Review which user roles can access the post types where the shortcode is used.
    Affected if Contributor-level users can create or edit posts/pages containing the [social] shortcode.

You are affected if the Advanced Social Media Icons plugin version 1.2 or lower is installed and any page contains a [social] shortcode with unsanitized attributes that could contain injected scripts.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input sanitization using WordPress sanitization functions (such as sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr, esc_js) for all user-supplied shortcode attributes before rendering.

Recommended fix Moderate confidence

Version 1.3 or later of the Advanced Social Media Icons plugin

  1. 1. Log in to the WordPress admin dashboard with Contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Advanced Social Media Icons' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly on the site

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7659 — 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-2026-7659 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