dbcve.org
Affiliate ToolkitWordPress extension · Servit

CVE-2023-23786

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to after 3.3.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Christof Servit affiliate-toolkit plugin <= 3.3.3 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 · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in the affiliate-toolkit WordPress plugin allows authenticated users with editor-level privileges or higher to inject malicious JavaScript code through plugin input fields, which is then stored and executed when other users view the affected content.

MitigationUpdate the affiliate-toolkit plugin to a version newer than 3.3.3; audit existing plugin data and content for any injected scripts; consider implementing additional input sanitization as a defense-in-depth measure.

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
Affiliate ToolkitWordPress extension
Affected:<= 3.3.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the affiliate-toolkit plugin is installed
    Navigate to WordPress admin panel > Plugins > Installed Plugins and locate 'Servit Affiliate Toolkit' or 'affiliate-toolkit' in the list. Note the installed version number displayed.
    Affected if The plugin is present and the version listed is 3.3.3 or lower.
  2. Verify the vulnerable version is in use
    Compare the installed version from step 1 against the affected version range: versions 3.3.3 and below are vulnerable to CVE-2023-23786.
    Affected if The installed version number is 3.3.3 or lower (e.g., 3.3.0, 3.2.9, etc.).
  3. Check current user privilege level
    In the WordPress admin panel, go to Users > All Users and identify your account or any account you are auditing. Click on the user and view the Role assigned (e.g., Administrator, Editor, Author, Contributor, Subscriber).
    Affected if The user has Editor, Author, or Administrator role, as these privilege levels allow access to the vulnerable plugin input fields.
  4. Locate plugin input fields that accept and store user input
    Access the affiliate-toolkit plugin settings panel in the WordPress admin (typically under a menu item like 'Affiliate Toolkit' or 'ATK'). Identify any form fields where data is entered and saved, such as affiliate link fields, product settings, or toolkit configuration inputs.
    Affected if The plugin input fields are accessible and functional, indicating the XSS attack surface exists.
  5. Inspect stored plugin data for suspicious scripts
    Examine the content where affiliate-toolkit data is displayed on your site (e.g., affiliate links, toolkit-generated content pages). View the page source or inspect elements to look for script tags, event handlers like onload/onerror, or encoded JavaScript payloads that may have been injected.
    Affected if Stored XSS payloads are present in plugin data or displayed content, confirming active exploitation of CVE-2023-23786.

A user is affected if the affiliate-toolkit plugin version is 3.3.3 or lower, a user with editor-level or higher privileges has access to the plugin input fields, and malicious scripts are found stored in plugin data or rendered on site pages.

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 3.3.3
Interim mitigation

Update the affiliate-toolkit plugin to a version newer than 3.3.3; audit existing plugin data and content for any injected scripts; consider implementing additional input sanitization as a defense-in-depth measure.

Recommended fix Moderate confidence

Version greater than 3.3.3 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Affiliate Toolkit plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completes successfully
  6. 6. Test the plugin functionality to ensure proper operation

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

Fix this in Affiliate Toolkit 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-2023-23786 — 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-23786 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