CVE-2026-3349
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe MinhNhut Link Gateway plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'url' parameter on the redirect page in all versions up to, and including, 3.6.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe MinhNhut Link Gateway WordPress plugin fails to properly sanitize and escape the 'url' parameter on its redirect page, allowing unauthenticated attackers to inject malicious JavaScript code via a crafted URL. When victims click the malicious link, the injected scripts execute in their browsers, potentially stealing session cookies or performing actions on behalf of the user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if MinhNhut Link Gateway plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'minhnhut-link-gateway' or similar.Affected if The plugin appears in the installed plugins list or the plugin folder exists in the WordPress plugins directory.
-
Identify the installed plugin versionIn the WordPress admin, find the plugin in the plugins list and view the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (e.g., minhnhut-link-gateway.php) and look for the 'Version' header in the plugin comment block.Affected if The version number displayed is lower than the current patched version or cannot be determined (indicating an unpatched release).
-
Locate the redirect functionalityInspect the plugin files for a redirect page or handler that processes a 'url' parameter. Look for files containing 'redirect', 'url', or 'go' in their names, or search the plugin source code for $_GET['url'] or $_REQUEST['url'] usage.Affected if The plugin contains a redirect page or function that accepts and processes a 'url' parameter without evident sanitization.
-
Verify if the redirect endpoint is publicly accessibleTest accessing the suspected redirect URL directly, such as /?page=minhnhut-link-gateway-redirect or a similar path shown in the plugin code, by appending a test url parameter (e.g., ?url=test).Affected if The redirect endpoint responds and processes the url parameter without requiring authentication.
-
Test for XSS vulnerability in the url parameterSafely inspect the redirect page response when a crafted url parameter is supplied. View the page source or observe whether the url value is reflected unescaped in the HTML output. Do not execute any injected scripts.Affected if The url parameter value is reflected in the page output without proper encoding or sanitization (e.g., <script> tags appear literally in the source or the injected content executes).
If the MinhNhut Link Gateway plugin is installed, uses an unpatched version, exposes a publicly accessible redirect page with a 'url' parameter, and reflects that parameter unescaped in output, then the environment is affected by CVE-2026-3349.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the MinhNhut Link Gateway plugin to the latest version immediately. Until then, users should avoid clicking untrusted links pointing to affected sites, and administrators should consider temporarily disabling the plugin.
Latest version of MinhNhut Link Gateway plugin (newer than 3.6.1)
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate 'MinhNhut Link Gateway' plugin
- Check if an update is available and update to the latest version
- If no update is visible in WordPress, manually download the latest version from the WordPress Plugin Repository at plugins.trac.wordpress.org
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3349 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data