CVE-2026-3348
Stored XSS in MinhNhut Link Gateway WordPress Plugin
Publication date: 2026-05-27
Last updated on: 2026-05-27
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| minhnhut | link_gateway | to 3.6.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The MinhNhut Link Gateway plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in its settings fields such as Description and Title. This vulnerability exists in all versions up to and including 3.6.1 due to insufficient input sanitization and output escaping.
Authenticated users with Administrator-level access or higher can exploit this vulnerability to inject arbitrary web scripts into pages. These scripts execute whenever a user accesses the redirect page.
This issue specifically affects multi-site WordPress installations and installations where the unfiltered_html capability has been disabled.
How can this vulnerability impact me? :
This vulnerability allows attackers with administrator privileges to inject malicious scripts that execute in the context of users visiting the affected redirect pages.
Such script execution can lead to unauthorized actions, data theft, session hijacking, or defacement of the website.
Because the vulnerability requires high privileges and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant for affected environments.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the MinhNhut Link Gateway plugin for WordPress to a version later than 3.6.1 where the issue is fixed.
Additionally, ensure that your WordPress installation is not a multi-site setup or that the unfiltered_html setting is enabled, as the vulnerability only affects multi-site installations or those with unfiltered_html disabled.
Limit Administrator-level access to trusted users only, since exploitation requires authenticated users with such privileges.