dbcve.org
NewslettersWordPress extension · Tribulant

CVE-2024-35718

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 4.9.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 (XSS or 'Cross-site Scripting') vulnerability in Tribulant Newsletters allows Reflected XSS.This issue affects Newsletters: from n/a through 4.9.5.

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

Reflected XSS vulnerability in the Tribulant Newsletters WordPress plugin where user-supplied input is not properly sanitized before being reflected back in the web page output. An attacker could inject malicious JavaScript that executes in the context of a victim's browser.

MitigationUpdate to the latest version of Tribulant Newsletters plugin that addresses this XSS vulnerability. Until patched, users should avoid clicking untrusted links and implement Content Security Policy headers.

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
NewslettersWordPress extension
Affected:< 4.9.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 Tribulant Newsletters plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Tribulant Newsletters' in the list of installed plugins.
    Affected if The plugin is not listed in the installed plugins
  2. Confirm the plugin is active
    In the same Plugins list, check whether Tribulant Newsletters shows as 'Active' under the plugin status column.
    Affected if The plugin is active and processing requests
  3. Identify the installed plugin version
    In the Plugins list, locate the version number displayed beneath the plugin name 'Tribulant Newsletters'. Alternatively, check the plugin's main PHP file header for the 'Version' tag, typically found in the plugin directory (e.g., /wp-content/plugins/newsletters-lite/ or /wp-content/plugins/newsletters/).
    Affected if A version number is returned that is less than 4.9.6 or the version cannot be determined (indicating an outdated release)
  4. Compare version against affected range
    Take the identified version number and compare it numerically against 4.9.6. Any version below 4.9.6 (such as 4.9.5, 4.9.0, 4.8.x, etc.) falls within the affected range.
    Affected if The installed version is lower than 4.9.6

The environment is affected if the Tribulant Newsletters plugin is active and the installed version is below 4.9.6.

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 4.9.6 or later
Fixed in 4.9.6
Interim mitigation

Update to the latest version of Tribulant Newsletters plugin that addresses this XSS vulnerability. Until patched, users should avoid clicking untrusted links and implement Content Security Policy headers.

Recommended fix High confidence

Newsletters plugin version 4.9.6

  1. Backup your WordPress site and database before updating
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find the 'Newsletters' plugin by Tribulant
  4. Check if current version is below 4.9.6
  5. Click 'Update now' to upgrade to version 4.9.6
  6. Verify the update completed successfully
  7. Test that the newsletters functionality works correctly after update

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

Fix this in Newsletters 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 the upgrade done

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-2024-35718 — 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-35718 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