CVE-2026-3659
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 WP Circliful plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' shortcode attribute of the [circliful] shortcode and via multiple shortcode attributes of the [circliful_direct] shortcode in all versions up to and including 1.2. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. Specifically, in the circliful_shortcode() function, the 'id' attribute value is concatenated directly into an HTML id attribute (line 285) without any escaping, allowing an attacker to break out of the double-quoted attribute and inject arbitrary HTML event handlers. Similarly, the circliful_direct_shortcode() function (line 257) outputs all shortcode attributes directly into HTML data-* attributes without escaping. This makes it possible for authenticated attackers, with Contributor-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 confidenceThe WP Circliful plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization and output escaping. The [circliful] shortcode's 'id' attribute is directly concatenated into HTML id attributes without escaping (line 285), while the [circliful_direct] shortcode outputs all attributes into data-* attributes without escaping (line 257). Authenticated attackers with Contributor-level access can inject arbitrary JavaScript via crafted shortcode attributes that execute when users view injected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Circliful plugin is installedNavigate to WordPress Admin > Plugins and look for 'WP Circliful' in the installed plugins listAffected if Plugin is installed and active
-
Identify the installed plugin versionClick on the plugin name in the plugins list to view details, or check the plugin header in wp-content/plugins/wp-circliful/plugin.php for the 'Version' commentAffected if Version matches or falls within the affected range (check against any known vulnerable versions for this plugin)
-
Check for shortcode usage in posts/pagesQuery the WordPress database: SELECT ID, post_title, post_content FROM wp_posts WHERE post_content LIKE '%[circliful%' OR post_content LIKE '%[circliful_direct%' AND post_status = 'publish'Affected if Published content contains the [circliful] or [circliful_direct] shortcode
-
Inspect shortcode attributes for potential injectionReview the shortcode content found in post_content for the 'id' attribute and other attributes, looking for unescaped quotes or suspicious JavaScript patternsAffected if Shortcode attributes contain unescaped special characters or appear to contain injected script tags
-
Verify user access levelsCheck WordPress user roles at Users > All Users to see if any Contributor-level users exist who could inject malicious shortcode contentAffected if Untrusted Contributor-level or higher users have access to create or edit content containing shortcodes
A user is affected if the WP Circliful plugin is installed with a vulnerable version AND shortcode content exists in published posts that could contain unsanitized attributes, particularly the 'id' attribute on the [circliful] shortcode.
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 · scopedEscape all shortcode attributes using WordPress's esc_attr() function before outputting them into HTML id and data-* attributes. Validate and sanitize input according to WordPress best practices. Consider implementing capability checks for shortcode usage.
version 1.3 or later (check WordPress plugin repository for latest available version)
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the WP Circliful plugin
- 4. Check if an update to version 1.3 or higher is available
- 5. If available, update the plugin to the latest version
- 6. If no update is available, consider using an alternative plugin or implementing additional output escaping via a custom security plugin or theme functions.php
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-3659 — 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-3659 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