CVE-2026-25310
Awaiting Analysis Awaiting Analysis - Queue
Server-Side Request Forgery in Alobaidi Extend Link

Publication date: 2026-02-19

Last updated on: 2026-02-19

Assigner: Patchstack

Description
Server-Side Request Forgery (SSRF) vulnerability in Alobaidi Extend Link extend-link allows Server Side Request Forgery.This issue affects Extend Link: from n/a through <= 2.0.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-19
Last Modified
2026-02-19
Generated
2026-05-07
AI Q&A
2026-02-19
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
alobaidi extend_link to 2.0.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-25310 is a Server Side Request Forgery (SSRF) vulnerability in the WordPress Extend Link Plugin versions up to and including 2.0.0.

This vulnerability allows a malicious actor to cause the affected website to make HTTP requests to arbitrary domains controlled by the attacker.

Exploitation of this flaw could enable the attacker to access sensitive information from other services running on the same system as the WordPress site.

The vulnerability is classified under the OWASP Top 10 category A10: Server-Side Request Forgery (SSRF).


How can this vulnerability impact me? :

If exploited, this vulnerability could allow an attacker to make the affected website send HTTP requests to attacker-controlled domains.

This could lead to unauthorized access to sensitive information from other services running on the same system as the WordPress site.

However, the vulnerability has a low severity impact with a CVSS score of 4.9 and requires only contributor or developer privileges to exploit.

It is considered unlikely to be exploited with significant impact.

Users are advised to update to version 2.0.1 or later of the plugin to mitigate this risk.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability allows an attacker to cause the affected website to make HTTP requests to arbitrary domains. Detection can involve monitoring outgoing HTTP requests from the WordPress site to unusual or unexpected external domains.

Since the vulnerability requires contributor or developer privileges to exploit, reviewing user activity logs for suspicious actions related to the Extend Link plugin may help.

Specific commands are not provided in the available resources.


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to update the Extend Link plugin to version 2.0.1 or later, where the vulnerability is resolved.

Using automated update tools such as those offered by Patchstack can facilitate rapid patching of the vulnerable plugin.

Additionally, limiting contributor or developer privileges to trusted users can reduce the risk of exploitation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart