Outbound Link ManagerWordPress extension · Sparro
CVE-2023-41850
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 Morris Bryant, Ruben Sargsyan Outbound Link Manager plugin <= 1.2 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Outbound Link Manager plugin for WordPress allows attackers to trick authenticated administrators into unknowingly submitting malicious requests to modify, add, or delete outbound links. The lack of proper anti-CSRF token validation on the plugin's administrative actions enables this attack.
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
Outbound Link ManagerWordPress extension
<= 1.2CVSS 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.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Sparro Outbound Link Manager' or 'Outbound Link Manager' in the list. Alternatively, check if the folder /wp-content/plugins/sparro-outbound-link-manager/ or similar exists on the server.Affected if The plugin is not found in the installed plugins list.
-
Check installed versionIn the WordPress plugins admin page, locate the Outbound Link Manager plugin and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually found in the plugin directory as index.php or sparro-outbound-link-manager.php) and look for the 'Version' header in the plugin comment block.Affected if The version listed is 1.2 or lower.
-
Verify plugin is activeIn WordPress admin > Plugins > Installed Plugins, check if Outbound Link Manager shows 'Active' status, or query the wp_options table for the option_name 'active_plugins' to see if the plugin is enabled.Affected if The plugin is active and running.
-
Check for non-protected admin actionsExamine the plugin PHP source code for state-changing functions (add, edit, delete link operations) and verify if they include wp_verify_nonce or check_admin_referer calls. Look for nonce fields in the plugin admin forms.Affected if No nonce verification is found on administrative action functions and forms.
If the Outbound Link Manager plugin is installed with version 1.2 or lower and is active, the environment is affected by this CSRF vulnerability.
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.
From vendor dataUpdate the Outbound Link Manager plugin to the latest version if a patch is available; otherwise, disable the plugin until a fix is released. Implement WordPress nonces on all state-changing forms as an immediate workaround.
Fix this in Outbound Link Manager
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41850 — 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-2023-41850 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