CVE-2026-25306
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in 8theme XStore Core et-core-plugin allows Reflected XSS.This issue affects XStore Core: from n/a through <= 5.6.4.
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 · moderate confidenceReflected XSS vulnerability in 8theme XStore Core plugin (et-core-plugin) versions through 5.6.4 allows attackers to inject malicious scripts via unsanitized user input that gets reflected in web 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 XStore Core plugin is installedCheck the WordPress plugins directory for 'et-core-plugin' or 'XStore Core' in wp-content/plugins/, or query the WordPress database: SELECT plugin_name FROM wp_plugins WHERE plugin_name LIKE '%xstore%' OR plugin_name LIKE '%et-core%';Affected if Plugin is present in the WordPress installation
-
Identify installed version numberCheck the plugin main file header (usually et-core-plugin/et-core.php) for 'Version:' comment, or query: SELECT meta_value FROM wp_options WHERE option_name LIKE '%plugin%version%'; Compare the version string to 5.6.4.Affected if Version is 5.6.4 or lower (any version through 5.6.4)
-
Locate user input reflection pointsSearch plugin source code for $_GET, $_POST, or $_REQUEST usage that outputs directly to page without esc_html, esc_attr, or sanitize_text_field. Focus on files in the plugin directory: grep -r '\$_GET\|\$_POST\|\$_REQUEST' --include='*.php' within the et-core-plugin folder.Affected if Code reflects raw $_GET/$_POST/$_REQUEST parameters directly into HTML output without sanitization
-
Test for reflected XSS parameterIdentify URL parameters on front-end pages (such as search, sort, or filter parameters) that might be reflected. Use browser DevTools or a proxy to observe if submitted values appear in the page response. Craft a test payload like <script>alert(1)</script> in suspected parameters and check if it executes or appears unescaped in the response.Affected if User-supplied parameter values appear in the HTML response without HTML encoding
-
Audit admin or frontend pages with user dataReview page templates and shortcodes provided by XStore Core that handle user data: search forms, product filters, ajax handlers. Check if these endpoints output user input via echo or print statements without escaping functions.Affected if Any endpoint outputs user input without esc_html(), esc_attr(), or equivalent sanitization
You are affected if the XStore Core (et-core-plugin) is installed at version 5.6.4 or lower AND any page/parameter reflects user input without HTML encoding.
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 to patched version of XStore Core when available; until then, implement output encoding (esc_html, esc_attr) on all user input reflection points and consider deploying WAF rules to block XSS payloads.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25306 — 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-25306 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