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

CVE-2026-3228

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-10
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 NextScripts: Social Networks Auto-Poster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `[nxs_fbembed]` shortcode in all versions up to, and including, 4.4.6. This is due to insufficient input sanitization and output escaping on the `snapFB` post meta value. 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 NextScripts Social Networks Auto-Poster plugin for WordPress contains a stored XSS vulnerability in the [nxs_fbembed] shortcode handler. Authenticated attackers with Contributor-level access can inject malicious scripts via the snapFB post meta value due to missing input sanitization and output escaping. When users access pages containing the shortcode, the injected scripts execute in their browsers.

MitigationUpgrade the plugin to version 4.4.7 or later once available. As an interim measure, audit posts using the [nxs_fbembed] shortcode and remove any suspicious snapFB meta values.

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. Verify the plugin is installed and get its version
    In WordPress admin, go to Plugins > Installed Plugins. Find 'NextScripts Social Networks Auto-Poster' and note the version number displayed below the plugin name.
    Affected if The plugin is installed and the version is lower than 4.4.7 (the version that contains the fix).
  2. Check for posts using the vulnerable shortcode
    In WordPress admin, go to Posts > All Posts. Search for posts containing the text '[nxs_fbembed]' using the search box, or use a database query: SELECT * FROM wp_posts WHERE post_content LIKE '%[nxs_fbembed]%' AND post_status != 'trash'.
    Affected if Any posts contain the [nxs_fbembed] shortcode, indicating potential exposure to the XSS vulnerability.
  3. Inspect snapFB post meta values for suspicious content
    Use a database query to examine snapFB meta values: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = 'snapFB' OR meta_key = 'snapFB_enable'. Look for meta values containing script tags, javascript:, onload, onerror, or other HTML/script injections.
    Affected if The snapFB meta value contains unsanitized JavaScript code, HTML tags, or suspicious patterns that could execute as XSS.
  4. Check user roles with access to post editing
    Review user accounts with Contributor-level or higher access at Users > All Users. Contributors can edit their own posts and may be able to exploit this vulnerability.
    Affected if There are users with Contributor-level access who could potentially inject malicious content via the vulnerable shortcode.

A user is affected if the plugin is installed with a version below 4.4.7 AND any posts contain the [nxs_fbembed] shortcode with unsanitized snapFB meta values that could execute malicious 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

Upgrade the plugin to version 4.4.7 or later once available. As an interim measure, audit posts using the [nxs_fbembed] shortcode and remove any suspicious snapFB meta values.

Recommended fix Moderate confidence

Version 4.4.7 or later of the NextScripts: Social Networks Auto-Poster plugin

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'NextScripts: Social Networks Auto-Poster' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. After updating, verify the plugin version is 4.4.7 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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