LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24623: WordPress Neoforum plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in saeros1984 Neoforum neoforum allows Reflected XSS.This issue affects Neoforum: from n/a through <= 1.0.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24623 is a reflected cross-site scripting issue in the WordPress Neoforum plugin through version 1.0. An attacker may lure a user into opening a crafted link, causing script to run in that user’s browser. Sources do not state active exploitation or name a fixed version.

Executive priority

Treat this as a high-priority plugin exposure if Neoforum is deployed on public WordPress sites. The business risk is user-targeted browser compromise and possible session or content manipulation. Urgency is lower where the plugin is absent or disabled, but source data does not identify a patch, so ownership should be assigned promptly.

Technical view

The issue is CWE-79 improper input neutralization during web page generation. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, scope changed, and low confidentiality, integrity, and availability impact. The affected product is listed as saeros1984 Neoforum, package neoforum, through <= 1.0.

Likely exposure

Exposure is limited to WordPress sites with the Neoforum plugin installed, especially version 1.0 or earlier. Public-facing WordPress sites are more relevant because the attack vector is network-based. The source data has some version metadata inconsistency, so confirm installed plugin identity and version directly.

Exploitation context

The attack requires user interaction, such as a victim visiting an attacker-controlled or crafted URL. It does not require attacker authentication. The CVE is not listed as KEV in the provided data, and the sources do not claim active exploitation.

Researcher notes

Key uncertainty: the description says Neoforum through <= 1.0, while the affected version object lists version 0 with defaultStatus unaffected. Use the CVE and Patchstack pages as the authoritative starting points, but verify plugin slug, code lineage, and any vendor release notes before concluding remediation status.

Mitigation direction

  • Inventory WordPress sites for the Neoforum plugin and record installed versions.
  • Check Patchstack and vendor guidance for a fixed release or official mitigation.
  • If no fix is available, consider disabling or removing the plugin where business impact allows.
  • Prioritize public-facing sites and administrator-heavy workflows for review.

Validation and detection

  • Confirm whether Neoforum is installed on each WordPress instance.
  • Verify the installed version against the affected range described in the CVE and Patchstack entry.
  • Review whether a vendor-supported fixed version has been published.
  • Check security monitoring for unusual links or browser-side script alerts involving Neoforum pages.
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-24623 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-24623Attack 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
saeros1984Neoforumneoforum, 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.