LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24980: WordPress Visionary Core plugin <= 1.4.9 - Reflected Cross Site Scripting (XSS) vulnerability

Improper 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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24980 is a reflected cross-site scripting issue in the WordPress Visionary Core plugin by NooTheme, affecting versions up to 1.4.9. An attacker could trick a user into opening a crafted link, causing script to run in that user’s browser. The public sources do not report active exploitation.

Executive priority

Treat as a high-priority WordPress plugin issue where the plugin is present. It is not currently supported by provided evidence as actively exploited, but reflected XSS can affect administrators and site users if phishing succeeds.

Technical view

The issue is CWE-79 improper input neutralization during web page generation in noo-visionary-core. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, and scope changed, with low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites using the NooTheme Visionary Core plugin at version 1.4.9 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.

Exploitation context

Successful exploitation requires user interaction, such as convincing a victim to visit a crafted URL. Sources do not indicate CISA KEV listing or confirmed active exploitation. Impact is typical of reflected XSS: session abuse, content manipulation, or actions in the victim’s browser context.

Researcher notes

The source bundle provides CVSS, CWE, affected plugin name, and affected range, but not the vulnerable parameter, fixed version, or proof-of-concept details. Avoid assumptions about patches or exploitation until Patchstack, NooTheme, or CVE records add details.

Mitigation direction

  • Inventory WordPress sites for the Visionary Core / noo-visionary-core plugin.
  • Identify installed plugin versions and prioritize any version 1.4.9 or earlier.
  • Check NooTheme, WordPress admin, and Patchstack for fixed-version guidance.
  • If no fix is available, evaluate disabling or removing the plugin until vendor guidance is clear.
  • Restrict administrative access and reinforce user phishing awareness while remediation is pending.

Validation and detection

  • Confirm whether noo-visionary-core is installed on each WordPress instance.
  • Record the installed version and compare it to the affected range through 1.4.9.
  • Review vendor or Patchstack advisories for current remediation status.
  • Check web logs for unusual requests targeting plugin-related pages or parameters.
  • Verify the CVE is not listed in CISA KEV before claiming active exploitation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24980 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-24980Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NooThemeVisionary Corenoo-visionary-core, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.