dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-13334

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 · unedited
The Mang Board WP plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'stag' parameter in all versions up to, and including, 2.3.4 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 confidence

The Mang Board WP WordPress plugin fails to sanitize the 'stag' parameter input and escape output, allowing unauthenticated attackers to inject malicious JavaScript via reflected XSS. Successful exploitation requires tricking a user into clicking a crafted link.

MitigationUpdate the plugin to a version newer than 2.3.4. If no update is available, implement proper input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the 'stag' parameter.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Mang Board WP plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Mang Board WP' or 'Mang Board' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'mangboard' or similar.
    Affected if The plugin is found in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view details, which typically displays the version number. Alternatively, open the main plugin file (e.g., mangboard.php) in wp-content/plugins/mangboard/ and look for the 'Version' header in the plugin comment block.
    Affected if The version number cannot be determined or is 2.3.4 or lower
  3. Verify the 'stag' parameter handling exists in the plugin
    Examine the plugin source code, specifically files that handle URL parameters. Look for code that retrieves the 'stag' parameter using $_GET['stag'] or $_REQUEST['stag'] and outputs it without sanitization or escaping.
    Affected if The plugin code processes the 'stag' parameter and echoes it back without using sanitize_text_field, esc_html, or esc_attr
  4. Check if the vulnerable endpoint is accessible
    Visit the site and identify pages that use the Mang Board plugin (e.g., board listing pages). Append '?stag=test' to the URL of a page that loads the plugin and observe if the value appears in the page output.
    Affected if The 'stag' parameter value is reflected in the page output without proper encoding or escaping

If the installed version is 2.3.4 or lower AND the plugin processes the 'stag' parameter which gets reflected in the page without escaping, the environment is affected by this reflected XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version newer than 2.3.4. If no update is available, implement proper input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the 'stag' parameter.

Recommended fix Moderate confidence

Mang Board WP version 2.3.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Mang Board WP' in the plugin list
  4. Check if an update is available and update to version 2.3.5 or later
  5. Alternatively, go to Plugins > Add New > Upload and upload the latest version from the WordPress plugin repository
  6. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13334 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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