WordPress Security Bulletin: NextScripts: Social Networks Auto-Poster plugin (CVE-2026-3228)

On this page

Security Alert Summary

The NextScripts: Social Networks Auto-Poster plugin contains a stored cross-site scripting (XSS) vulnerability affecting versions up to and including 4.4.6. Authenticated users with Contributor-level access or higher can inject JavaScript via the plugin’s [nxs_fbembed] shortcode by manipulating the snapFB post meta value, causing scripts to run when an injected page is viewed.


CVE Details

  • CVE ID: CVE-2026-3228
  • Affected plugin / component: NextScripts: Social Networks Auto-Poster plugin for WordPress — specifically the [nxs_fbembed] shortcode and the snapFB post meta value
  • Affected versions: All versions up to, and including, 4.4.6
  • Published: March 10, 2026 at 6:19 PM UTC
  • Last modified: March 11, 2026 at 1:53 PM UTC
  • CVSS v3.1: Base Score 6.4, Severity MEDIUM — Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
  • Authentication / privileges / user interaction: Requires authentication. Privileges required: Low (authenticated users at Contributor level and above as stated in the description). User interaction: None.
  • Primary impact: Confidentiality: Low; Integrity: Low; Availability: None
  • CWE / weakness: CWE-79 (Cross-site Scripting)
  • Fixed version: Not specified in the CVE entry

Technical Details

This vulnerability is a stored cross-site scripting (XSS) issue caused by insufficient input sanitization and output escaping of the snapFB post meta value used by the plugin’s [nxs_fbembed] shortcode. Because the plugin stores attacker-controlled data in post meta without proper sanitization/escaping, an authenticated user with Contributor-level privileges or higher can insert arbitrary web scripts that are later rendered in the page context when the shortcode output is displayed.

The CVE description identifies the [nxs_fbembed] shortcode and the snapFB post meta as the vectors; no other functions, REST endpoints, or checks are named in the provided entry. The impact is limited to script execution in the context of pages that include the injected content — allowing actions an attacker can perform via injected JavaScript within the victim’s browser session.


How This Could Impact Your Website

In a typical small business WordPress site, contributors (e.g., content authors or external contractors) can create or edit posts. If a contributor submits content that includes a crafted snapFB value via the [nxs_fbembed] shortcode, that content could persist in the site database and run scripts when other users view the page.

A realistic scenario: an external contractor with Contributor access publishes or updates a post containing a malicious payload. When internal staff or the site owner view that post, the injected script may run and can be used to read page-visible data (for example, email addresses displayed on the page) or perform actions available to the viewer in their browser session consistent with the limited confidentiality and integrity impacts noted in the CVSS data. This increases the risk of targeted phishing or social-engineering attacks against staff and contributors.

If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available. (No fixed version is specified in the CVE entry.)
  • Review and reduce unnecessary user roles and capabilities, especially Contributor and higher accounts.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and logs for unusual behavior, including unexpected post meta changes or content edits.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References