LiveActive security incident?Get immediate response
CVE Record

CVE-2025-58196: WordPress UiCore Elements Plugin <= 1.3.4 - Cross Site Scripting (XSS) Vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in uicore UiCore Elements uicore-elements allows Stored XSS.This issue affects UiCore Elements: from n/a through <= 1.3.4.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

UiCore Elements for WordPress has a stored cross-site scripting issue through version 1.3.4. A lower-privileged authenticated user could store malicious page content that affects another user who views it. Business risk is moderate because exploitation needs plugin access and user interaction, but successful abuse could affect site integrity and user trust.

Executive priority

Treat as a moderate WordPress hygiene item. Prioritize internet-facing sites, marketing sites with many content users, and any property handling customer sessions or lead data. Do not treat as emergency exploitation without new evidence.

Technical view

CVE-2025-58196 is CWE-79 stored XSS in uicore-elements, affecting UiCore Elements versions through 1.3.4. CVSS 3.1 is 6.5 with AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, indicating network reachability, low complexity, required privileges, required victim interaction, and changed scope.

Likely exposure

Exposure is limited to WordPress sites running UiCore Elements version 1.3.4 or earlier. Sites with many contributor, author, editor, or site-builder accounts have higher practical exposure because privileges are required.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The vulnerability is plausible for authenticated content abuse, but no exploit details, affected functions, or confirmed attack campaign are provided in the bundle.

Researcher notes

The source bundle identifies stored XSS but does not provide vulnerable parameters, proof of concept, patch version, or official mitigation. Validation should stay inventory-focused and avoid offensive reproduction unless authorized in a controlled test environment.

Mitigation direction

  • Inventory WordPress sites for the uicore-elements plugin and version.
  • Check UiCore or Patchstack guidance for a fixed version or official mitigation.
  • Upgrade only to a vendor-confirmed fixed release when available.
  • Temporarily restrict plugin content-editing access to trusted administrators.
  • Disable the plugin where business risk exceeds dependency needs.

Validation and detection

  • Confirm whether UiCore Elements is installed on each WordPress property.
  • Flag any instance running version 1.3.4 or earlier.
  • Review which accounts can create or edit plugin-controlled content.
  • Inspect recent plugin-managed content for unexpected script-like markup.
  • Monitor vendor advisories for patch details not present in the source bundle.
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-2025-58196 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-58196Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
uicoreUiCore Elementsuicore-elements, 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.