dbcve.org
Better Anchor LinksWordPress extension · Ludek

CVE-2024-22287

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to after 1.7.5 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
Cross-Site Request Forgery (CSRF) vulnerability in Luděk Melichar Better Anchor Links allows Cross-Site Scripting (XSS).This issue affects Better Anchor Links: from n/a through 1.7.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

The Better Anchor Links WordPress plugin (versions up to 1.7.5) contains a CSRF vulnerability that enables injection of malicious JavaScript (XSS). An attacker can trick a logged-in administrator into submitting a crafted request that stores XSS payloads within plugin settings, which then executes when viewed.

MitigationUpdate to the latest plugin version if available, or implement proper nonce verification and CSRF token validation on all form submissions and AJAX actions within the plugin.

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
Better Anchor LinksWordPress extension
Affected:<= 1.7.5

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Better Anchor Links' by Ludek. Alternatively, check the /wp-content/plugins/ directory for a folder named 'better-anchor-links' or similar.
    Affected if The plugin is installed and active
  2. Check installed version
    In WordPress admin Plugins page, find Better Anchor Links and view the version number under the plugin name. Or read the main plugin PHP file header for 'Version:' tag.
    Affected if Version is 1.7.5 or lower, or version cannot be determined (treat as affected)
  3. Inspect plugin settings for stored scripts
    Navigate to the plugin settings page (likely under Settings > Better Anchor Links or similar). View the page source or inspect form fields for any suspicious <script> tags, event handlers (onclick, onerror, etc.), or encoded payloads in text inputs.
    Affected if Any JavaScript code or HTML tags are present in settings fields that were not intentionally added by the admin
  4. Check plugin source for CSRF protection
    If you have file access, examine the plugin's main PHP file(s) that handle form submissions. Search for 'wp_nonce_field', 'check_admin_referer', or 'check_ajax_referer' calls around form processing code.
    Affected if Form handling code lacks nonce verification functions, or nonce checks are present but improperly implemented

If the plugin is installed, version 1.7.5 or lower, and lacks proper nonce/CSRF protection in its settings handling code, the environment is vulnerable to stored XSS via CSRF.

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

Update to the latest plugin version if available, or implement proper nonce verification and CSRF token validation on all form submissions and AJAX actions within the plugin.

Recommended fix Moderate confidence

Update to the latest available version of Better Anchor Links (version greater than 1.7.5)

  1. Check the WordPress admin dashboard for plugin updates
  2. Navigate to Plugins > Installed Plugins > Better Anchor Links
  3. If an update is available, click 'Update Now' to update to the latest patched version
  4. Alternatively, navigate to Dashboard > Updates and update all plugins including Better Anchor Links
  5. After updating, verify the plugin is running on a version greater than 1.7.5

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

Fix this in Better Anchor Links Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22287 — 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-22287 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