dbcve.org
Social Networks Auto PosterWordPress extension · Nextscripts

CVE-2024-37275

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to after 4.4.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in NextScripts NextScripts social-networks-auto-poster-facebook-twitter-g allows DOM-Based XSS.This issue affects NextScripts: from n/a through <= 4.4.7.

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 confidence

DOM-Based Cross-site Scripting (XSS) vulnerability in the NextScripts social networks auto-poster WordPress plugin (versions through 4.4.7). The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that is directly manipulated in the browser's DOM without server-side validation.

MitigationSanitize and properly escape all user-supplied input before inserting it into DOM operations. Implement context-aware output encoding and use security-focused APIs (such as textContent instead of innerHTML) for DOM manipulation.

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
Social Networks Auto PosterWordPress extension
Affected:<= 4.4.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Nextscripts Social Networks Auto Poster' is active and installed
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    In Plugins list, find the version number listed for Nextscripts Social Networks Auto Poster. Compare it to the affected range: any version <= 4.4.6 is vulnerable
    Affected if The installed version is 4.4.6 or lower
  3. Identify DOM manipulation points
    Inspect the plugin's JavaScript files (typically in /wp-content/plugins/social-networks-auto-poster/) for innerHTML assignments using user-supplied data without sanitization. Search for patterns like element.innerHTML = userInput or similar DOM injection methods
    Affected if Code uses innerHTML with unsanitized request parameters or user input
  4. Confirm admin access exists
    Check if administrator or editor roles can access the plugin settings where user profiles or social network credentials are configured
    Affected if Administrators can input data that flows into the vulnerable DOM operations
  5. Verify no security plugin blocks exploitation
    Review any Web Application Firewall (WAF) or security plugin logs for attempts to exploit XSS parameters in requests to wp-admin/admin-ajax.php or plugin pages
    Affected if No WAF or input filtering is actively blocking malicious DOM injection attempts

If the Nextscripts Social Networks Auto Poster plugin version is 4.4.6 or lower and the plugin is active, the environment is affected by this DOM-based XSS vulnerability.

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
Upgrade available Upgrade to a release after 4.4.6
Interim mitigation

Sanitize and properly escape all user-supplied input before inserting it into DOM operations. Implement context-aware output encoding and use security-focused APIs (such as textContent instead of innerHTML) for DOM manipulation.

Recommended fix Moderate confidence

Social Networks Auto Poster version 4.4.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "Social Networks Auto Poster" in the plugin list
  4. Check if the current version is 4.4.6 or lower
  5. If vulnerable, click "Update Now" to update to the latest version
  6. Alternatively, download version 4.4.8 or later from the WordPress plugin repository and upload manually
  7. After update, verify the version number reflects the patched release

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

Fix this in Social Networks Auto Poster Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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