CVE-2023-46625

Autolinks Manager <= 1.10.04 - Cross-Site Request Forgery

2023-10-25 00:00
Skalucy

Strategic Overview

Status
Patched in 1.10.05
Affected Version
<= 1.10.04
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-46625
View all Link Manager – Analyze, Automate, and Monitor Links vulnerabilities

At a glance

CVE-2023-46625 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Link Manager WordPress plugin, affecting versions <= 1.10.04. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.10.05; sites on affected versions should update now. Disclosed October 2023, reported by Skalucy.

Vulnerability Overview

The Autolinks Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.10.04. This is due to missing or incorrect nonce validation in autolinks.php, categories.php, and term_groups.php. This makes it possible for unauthenticated attackers to add, clone, or delete autolinks, categories, and term groups via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Link Manager <= 1.10.04 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Link Manager the fix is 1.10.05: builds <= 1.10.04 are affected, anything from 1.10.05 onward is not.

Remediation

Update to version 1.10.05, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Link Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Link Manager 1.10.05 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C