elink – Embed Content <= 1.1.0 - Authenticated (Contributor+) Insufficient Input Validation
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- elink – Embed Content
- Affected Version
<= 1.1.0- CVSS
- 6.4Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2025-7507
At a glance
CVE-2025-7507 is a medium-severity Improper Input Validation vulnerability in the elink WordPress plugin, affecting versions <= 1.1.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2025, reported by Shreyas Malhotra.
Vulnerability Overview
The elink – Embed Content plugin for WordPress is vulnerable to Malicious Redirect in all versions up to, and including, 1.1.0. This is due to the plugin not restricting URLS that can be supplied through the elink shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to supply an HTML file that can be leverged to redirect users to a malicious domain.
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 interaction from a victim user.
CWE-20: Improper Input Validation
Reaching this weakness in elink <= 1.1.0 takes an account at Contributor level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. No fixed build of this plugin is recorded for elink yet, so installs running <= 1.1.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C