PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-100108 maxfoundry CVE debrief

The Social Share Buttons plugin for WordPress has a Stored Cross-Site Scripting vulnerability via the 'form (containing share_url)' parameter in all versions up to, and including, 1.30. This allows authenticated attackers with subscriber-level access and above to inject arbitrary web scripts in pages that execute when a user accesses an injected page.

Vendor
maxfoundry
Product
Social Share Buttons
CVSS
MEDIUM 6.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-16
Original CVE updated
2026-10-16
Advisory published
2026-10-16
Advisory updated
2026-10-16

Who should care

Defenders responsible for WordPress installations with the Social Share Buttons plugin should assess exposure and prioritize verification and remediation efforts. This includes operators managing WordPress environments, vulnerability management teams, security teams, and IT staff responsible for plugin updates and security configurations.

Why it matters

The Social Share Buttons plugin for WordPress has a Stored Cross-Site Scripting vulnerability allowing authenticated attackers to inject arbitrary web scripts. Defenders should prioritize verification and remediation efforts.

  • Defenders must verify plugin versions and user access levels to assess exposure
  • Injected scripts can execute on pages accessed by users
  • Remediation priority is high for WordPress installations with the plugin installed

Technical summary

The Social Share Buttons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form (containing share_url)' parameter in all versions up to, and including, 1.30. This is due to insufficient input sanitization and output escaping. Authenticated attackers with subscriber-level access and above can inject arbitrary web scripts in pages that execute when a user accesses an injected page. Exploitation requires that the 7-day review-nag timer has elapsed since the attacker's first wp-admin visit.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure based on the plugin version and user access levels.

Recommended defensive actions

  • Verify the Social Share Buttons plugin version and update to a patched version if necessary
  • Assess user access levels and restrict access to the plugin's functionality
  • Monitor for suspicious activity and injected scripts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in plugin versions up to 1.30. The CVE record and NVD entry provide details on the vulnerability. Additional verification is recommended to assess exposure and validate affected scope. Defenders should verify plugin versions, user access levels, and review official advisories for guidance. The 7-day review-nag timer and nonce requirements for exploitation should be considered during verification.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-100108 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-100108

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-100108 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-100108

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.