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

CVE-2026-13246

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 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 GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'block_id' (and other) shortcode attributes of the 'givewp_campaign_comments' shortcode in versions up to, and including, 4.16.0. This is due to insufficient input sanitization and output escaping on user supplied attributes in CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render(), where the blockId value is interpolated directly into a single-quoted HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 GiveWP WordPress plugin fails to sanitize and escape the block_id shortcode attribute in the givewp_campaign_comments shortcode. The blockId value is directly interpolated into a single-quoted HTML attribute without esc_attr() in CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render(), allowing authenticated authors+ to inject persistent JavaScript.

MitigationUpdate GiveWP plugin to a version beyond 4.16.0 where input sanitization and esc_attr() output escaping have been implemented for shortcode attributes.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 GiveWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate GiveWP, or check for /wp-content/plugins/give/ directory on the filesystem
    Affected if GiveWP plugin is not installed on the WordPress site
  2. Determine installed GiveWP version
    Check the plugin version in the WordPress plugins list, or read the main plugin file /wp-content/plugins/give/wp-content/plugins/give/give.php and look for the 'Version:' header comment
    Affected if Version is below 4.16.0 (the patched version)
  3. Locate use of the vulnerable shortcode
    Search WordPress database or content for [givewp_campaign_comments] shortcode usage in posts, pages, or widgets. Use SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%[givewp_campaign_comments%' (adjust prefix if needed)
    Affected if The shortcode with block_id attribute appears in any published content
  4. Inspect vulnerable code in CampaignCommentsShortcode
    In the plugin directory, locate CampaignCommentsShortcode.php (typically in /wp-content/plugins/give/src/Shortcodes/) and examine the parseAttributes() method for direct string interpolation without esc_attr()
    Affected if Code shows blockId/block_id directly inserted into HTML attributes without esc_attr() escaping

A site is affected if GiveWP plugin versions below 4.16.0 are installed AND the givewp_campaign_comments shortcode with a block_id attribute is in use, allowing authenticated authors+ to inject persistent JavaScript.

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 GiveWP plugin to a version beyond 4.16.0 where input sanitization and esc_attr() output escaping have been implemented for shortcode attributes.

Recommended fix Moderate confidence

GiveWP version > 4.16.0 (latest stable release)

  1. 1. Verify the currently installed GiveWP plugin version in WordPress admin under Plugins > Installed Plugins
  2. 2. Navigate to Plugins > Add New > Upload Plugin if an update is not available in the WordPress repository
  3. 3. Alternatively, check the WordPress plugin repository or GiveWP official website for the latest stable release
  4. 4. Update the GiveWP plugin to the latest version available (version higher than 4.16.0)
  5. 5. After updating, clear any site caching if applicable
  6. 6. Test the donation functionality and shortcodes to ensure the update did not break existing functionality
Caveat Review GiveWP changelog for potential breaking changes between 4.16.0 and the target upgrade version before proceeding

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13246 — 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-13246 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