CVE-2026-13710
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 Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Image Box widget's 'sg_body_description' parameter in versions up to, and including, 3.2.6. This is due to insufficient input sanitization and output escaping on the description attribute in the render_body() method of the Image_Box_View class — every other attribute used by the method is wrapped in esc_attr(), but the description value is concatenated directly into HTML body context. 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 Jeg Kit Elementor plugin versions up to 3.2.6 contain a Stored XSS vulnerability in the Image Box widget's 'sg_body_description' parameter. The render_body() method of Image_Box_View class directly concatenates the description value into HTML body context without escaping, while other attributes properly use esc_attr(), allowing authenticated attackers with Contributor-level access to inject malicious scripts.
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.
-
Confirm Jeg Kit plugin is installedCheck your WordPress plugins directory or wp-admin plugins list for 'Jeg Kit' or 'Jeg Elementor Kit'Affected if Plugin is installed and no version is visible or version is 3.2.6 or lower
-
Identify the installed Jeg Kit versionLook in the plugin file header (usually in main plugin file like jeg-kit.php) or WordPress plugin admin page for the version numberAffected if Version is 3.2.6 or any version up to 3.2.6
-
Determine if Image Box widget is in useSearch your WordPress database or page/post content for elementor data containing 'image-box' widget or review pages built with Elementor that use Jeg Kit widgetsAffected if Image Box widget from Jeg Kit is used in any post, page, or template
-
Inspect sg_body_description for unescaped contentExamine the database entries or exported content for the 'sg_body_description' field in any Image Box widget instances - look for unescaped HTML tags, script tags, or event handlersAffected if The sg_body_description field contains raw HTML, script tags, or javascript: URIs without proper encoding
You are affected if Jeg Kit plugin version is 3.2.6 or lower AND the Image Box widget with sg_body_description is in use on your site, as the description content is not escaped and could contain injected scripts.
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.
From vendor dataUpdate the Jeg Kit plugin to version 3.2.7 or later, which should include proper escaping for the description parameter using esc_html() or similar output encoding.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13710 — 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-13710 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