LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1792: Geo Widet <= 1.0 - Reflected Cross-Site Scripting

The Geo Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the URL path in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1792 affects the Geo Widget WordPress plugin up to version 1.0. An unauthenticated attacker may cause malicious scripts to run in a visitor’s browser if a user accesses an affected page. Business impact is mainly session theft, phishing, or content manipulation against site users, not direct server takeover.

Executive priority

Treat as a moderate web risk. Prioritize public-facing WordPress sites, especially those with authenticated users or administrative sessions. If the plugin is unused, remove it promptly; otherwise monitor vendor guidance and apply a fixed release when available.

Technical view

The source bundle describes a CWE-79 cross-site scripting issue in Geo Widget for WordPress, caused by insufficient input sanitization and output escaping around the URL path. CVSS 3.1 is 6.1 with network access, low complexity, no privileges, and required user interaction. Sources conflict on reflected versus stored wording, so classify as XSS with uncertain persistence.

Likely exposure

Exposure is limited to WordPress sites running the Geo Widget plugin version 1.0 or earlier. The provided affected-product metadata is inconsistent, so asset validation should rely on installed plugin name and version rather than CPE data.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. Exploitation requires a user to access an affected page or crafted path, after which script may execute in that user’s browser context.

Researcher notes

The bundle has wording inconsistencies: title says reflected XSS, while description says stored XSS via URL path. CVSS requires user interaction and no privileges. The WordPress Trac reference points to GeoWidget.php line 265, but the source bundle does not identify a patched version.

Mitigation direction

  • Inventory WordPress sites for the Geo Widget plugin and installed version.
  • If Geo Widget is installed at version 1.0 or earlier, prioritize removal or disabling.
  • Check WordPress plugin and vendor guidance for an updated fixed release.
  • Use compensating controls such as WAF XSS filtering where immediate removal is not possible.

Validation and detection

  • Confirm whether the geowidget plugin directory exists on each WordPress site.
  • Record the installed Geo Widget version from WordPress admin or plugin files.
  • Review plugin code paths referenced by WordPress Trac for unsanitized URL output.
  • Check access logs for suspicious requests targeting Geo Widget-related paths.
Prepared
Confidence
medium
Sources
4

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-1792 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
Medium
CVSS
6.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:N

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
3Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2026-1792Attack 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:N

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
owencutajarGeo Widget0unaffected
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.