CVE-2026-24980
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 NooTheme Visionary Core noo-visionary-core allows Reflected XSS.This issue affects Visionary Core: from n/a through <= 1.4.9.
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 NooTheme Visionary Core allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages. This occurs because the application fails to properly encode output when rendering user-supplied data, enabling session hijacking, credential theft, or defacement. The vulnerability affects all versions through 1.4.9.
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.
-
Identify if NooTheme Visionary Core is installedCheck the theme directory for the Visionary Core theme files, typically found in wp-content/themes/ or similar theme folder locationAffected if The theme is present in the WordPress installation
-
Determine the installed theme versionLocate the theme's style.css or version file and read the Version: header, or check theme configuration files for version metadataAffected if The version is 1.4.9 or lower (all versions through 1.4.9 are affected)
-
Identify user input fields that render outputReview theme template files (PHP files in the theme directory) for instances where $_GET, $_POST, or $_REQUEST variables are directly output to HTML without sanitization functionsAffected if User-supplied parameters are reflected in pages without esc_html, esc_attr, or similar encoding functions
-
Inspect search and query parameter handlingExamine PHP files that process search queries, URL parameters, or form submissions and output the values back to the pageAffected if Input such as search terms, filter values, or URL parameters appear in the rendered HTML without escaping
-
Check for missing output encoding in template filesSearch theme PHP files for echo statements that output request parameters or user data directly, looking for patterns like echo $_GET['param'] without sanitize or esc functionsAffected if Direct output of unsanitized user input is found in theme template files
A user is affected if NooTheme Visionary Core version 1.4.9 or lower is installed AND the theme reflects user-supplied input in web pages without proper output 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 dataApply output encoding/escaping functions (esc_html, esc_attr, wp_kses, or similar WordPress sanitization functions) to all user-controlled input before rendering in HTML context. Input validation should also be implemented as a defense-in-depth measure.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24980 — 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-24980 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