CVE-2024-12121
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 · uneditedThe Broken Link Checker | Finder plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.5.0 via the 'moblc_check_link' function. This makes it possible for authenticated attackers, with Author-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe Broken Link Checker | Finder WordPress plugin has a blind Server-Side Request Forgery (SSRF) vulnerability in the moblc_check_link function. Authenticated attackers with Author-level access or higher can make arbitrary web requests from the server, potentially querying internal services and exfiltrating sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Broken Link Checker | Finder' in the list. Note the installed version displayed.Affected if The plugin is listed and active in the WordPress installation.
-
Check plugin version against fixIn the plugins list, compare the installed version to version 2.5.1. The plugin version is shown under the plugin name. Versions prior to 2.5.1 are affected.Affected if The installed version is lower than 2.5.1.
-
Verify Author-level users existGo to WordPress admin > Users and review user accounts. Check the role assigned to each user account. Authors have the 'author' role capability.Affected if There are one or more users with Author role or higher (Editor, Admin) in the WordPress installation.
-
Confirm moblc_check_link function is exposedInspect the plugin files (typically in wp-content/plugins/broken-link-checker-finder/) for the moblc_check_link function. Check if it is hooked to an AJAX action (like wp_ajax_moblc_check_link) that is accessible without admin-level privileges. Look for add_action('wp_ajax_moblc_check_link', ...) calls.Affected if The moblc_check_link function is registered as an AJAX handler accessible to logged-in users with Author-level access.
Your environment is affected if the Broken Link Checker plugin is installed with a version lower than 2.5.1 and you have users with Author-level or higher access, as the vulnerable moblc_check_link function can be reached by such authenticated users.
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 plugin to version 2.5.1 or later when available. If no patch exists, disable the plugin until a fix is released. Implement strict URL validation and allowlisting for the moblc_check_link function to prevent requests to internal resources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12121 — 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-2024-12121 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