Affiliate ToolkitWordPress extension · Servit
CVE-2025-46231
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in SERVIT Software Solutions affiliate-toolkit affiliate-toolkit-starter allows Cross Site Request Forgery.This issue affects affiliate-toolkit: from n/a through <= 3.7.3.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in affiliate-toolkit Starter plugin versions through 3.7.3 allows remote attackers to trick authenticated administrators into performing unintended actions like modifying affiliate settings, changing commission rates, or manipulating affiliate accounts by forging 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
Affiliate ToolkitWordPress extension
< 3.7.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate affiliate-toolkit plugin installationCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'affiliate-toolkit' or similar variant like 'affiliate-toolkit-starter'. In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Affiliate Toolkit' or 'Servit Affiliate Toolkit'.Affected if The affiliate-toolkit plugin is found installed on the WordPress site
-
Identify installed version numberIn WordPress admin under Plugins > Installed Plugins, find the Affiliate Toolkit entry and read the version number displayed below the plugin name. Alternatively, check the main plugin PHP file header for 'Version:' tag.Affected if Version number is 3.7.3 or lower (any version through 3.7.3 is affected)
-
Confirm admin authentication requirementNote that this CSRF vulnerability requires an authenticated administrator to have an active session. Check if any administrator accounts have recently logged in or have persistent sessions on the WordPress site.Affected if Authenticated administrator sessions exist or are possible on the site
-
Verify affected version rangeCompare your installed version against the affected range: any version below 3.7.4 is vulnerable. Version 3.7.4 and above contain the fix.Affected if Installed version is less than 3.7.4
A site is affected if the affiliate-toolkit (Servit Affiliate Toolkit) plugin is installed with any version through 3.7.3 and has authenticated administrator access.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.7.4
Add anti-CSRF token validation (nonce checks) to all state-changing operations and configure SameSite attributes on session cookies to prevent cross-origin request forgery.
3.7.4
- Update the Affiliate Toolkit plugin to version 3.7.4 or later
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
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46231 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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