SurfLink < 2.6.0 - Missing Authorization to Authenticated (Subscriber+) 410 Gone URL Import via 'surfl_import_410' AJAX Action
The SurfLink - Ultimate Link Manager plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the ajax_import_410() function in all versions up to 2.6.0. This is due to a missing capability check (current_user_can()) and missing nonce verification (check_ajax_referer()) in the ajax_import_410() function, while all other AJAX handlers in the same class (ajax_add_single_410, ajax_save_editted_410, ajax_delete_410, ajax_bulk_410_delete, ajax_empty_410, ajax_export_410) properly implement both authorization and nonce checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to import arbitrary URLs into the 410 Gone database table via the surfl_import_410 AJAX action. Injected URLs will cause the site to return HTTP 410 Gone responses to all visitors accessing those paths, potentially causing denial of service for legitimate pages and SEO damage through search engine delisting.
Quick answer
SurfLink – Link Manager & Backup Restore should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- [*, 2.6.0)
Fixed versions
- 2.6.0
How to fix it
SurfLink – Link Manager & Backup Restore is affected by CVE-2026-3552, a authorization bypass issue in [*, 2.6.0). Wordfence lists the official remediation as updating to version 2.6.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has SurfLink – Link Manager & Backup Restore installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
- Confirm the installed SurfLink – Link Manager & Backup Restore version and compare it with the affected range from the Wordfence advisory.
- Update SurfLink – Link Manager & Backup Restore to version 2.6.0, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable SurfLink – Link Manager & Backup Restore or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, tickets, marketplace actions, and admin actions for unauthorized activity.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, booking/support plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running SurfLink – Link Manager & Backup Restore version is version 2.6.0 or newer, and record the patched version in the remediation ticket.
- Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, payment, booking, ticket, import/export, snippet, or settings change.
- Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-3552?
SurfLink – Link Manager & Backup Restore versions listed as affected should be reviewed: [*, 2.6.0).
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.