dbcve.org
SendpressWordPress extension · Pressified

CVE-2023-47517

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 1.23.11.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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in SendPress Newsletters plugin <= 1.23.11.6 versions.

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

This is an unauthenticated reflected cross-site scripting (XSS) vulnerability in the SendPress Newsletters WordPress plugin. The vulnerability allows an attacker to inject malicious JavaScript code through URL parameters, which is then reflected back in the plugin's response without proper sanitization or output encoding.

MitigationUpdate the SendPress Newsletters plugin to a version newer than 1.23.11.6. Until patched, implement a WAF rule or content security policy to filter malicious script parameters in requests.

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
SendpressWordPress extension
Affected:<= 1.23.11.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 SendPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SendPress Newsletters' or 'Pressified Sendpress' in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    Click on the plugin name in the WordPress plugins list to view the version number, or inspect the plugin header in wp-content/plugins/sendpress-newsletters/sendpress.php for the 'Version' field
    Affected if Version is 1.23.11.6 or lower
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the SendPress plugin shows as 'Active' rather than 'Inactive'
    Affected if Plugin status is Active
  4. Identify vulnerable endpoint exposure
    Access the SendPress public-facing pages or check if the plugin handles URL parameters in requests (common paths include /?sp-action=..., /?page=sendpress, or AJAX endpoints)
    Affected if Plugin responds to web requests and reflects URL parameters in output without encoding

You are affected if SendPress Newsletters plugin is installed, active, and running version 1.23.11.6 or lower, with the vulnerable parameter reflection feature accessible via web requests.

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.

From vendor data
Upgrade available Upgrade to a release after 1.23.11.6
Interim mitigation

Update the SendPress Newsletters plugin to a version newer than 1.23.11.6. Until patched, implement a WAF rule or content security policy to filter malicious script parameters in requests.

Fix this in Sendpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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