LiveActive security incident?Get immediate response
CVE Record

CVE-2025-30961: WordPress Trackserver plugin <= 5.1.0 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in tinuzz Trackserver trackserver allows DOM-Based XSS.This issue affects Trackserver: from n/a through <= 5.1.0.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-30961 is a DOM-based cross-site scripting issue in the WordPress Trackserver plugin. A successful attack could make a victim’s browser run attacker-controlled script in the site context, with limited confidentiality, integrity, and availability impact. The provided sources do not show active exploitation or a confirmed fixed version.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Prioritize internet-facing or customer-trusted sites using Trackserver, but do not classify it as emergency-level based on the supplied evidence.

Technical view

The CVE describes improper neutralization during web page generation in tinuzz Trackserver, categorized as CWE-79. The CVSS 3.1 score is 6.5, with network attack vector, low complexity, low privileges required, and user interaction required. The bundle states affected Trackserver versions are through 5.1.0, while the Patchstack URL text references 5.0.3.

Likely exposure

Exposure is limited to WordPress sites running the tinuzz Trackserver plugin in affected versions. The source bundle does not provide CPEs or deployment prevalence. Sites without this plugin are not indicated as affected.

Exploitation context

The CVSS vector supports a scenario requiring low privileges and victim interaction. The issue is not listed in KEV, and the provided sources do not claim active exploitation or public exploit availability.

Researcher notes

Key uncertainty is version and remediation detail. The CVE bundle says through 5.1.0, while the Patchstack reference URL names 5.0.3. No exploit details, patch version, or active exploitation evidence are provided in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Trackserver plugin and installed version.
  • Check vendor and Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove Trackserver where it is not business-critical.
  • Limit low-privilege WordPress account access until remediation is confirmed.
  • Review exposed Trackserver pages for unnecessary public access.

Validation and detection

  • Confirm whether Trackserver is installed on each WordPress property.
  • Record plugin versions and flag installations through 5.1.0.
  • Verify whether vendor guidance identifies a safe upgraded version.
  • Review relevant WordPress content and logs for suspicious Trackserver-linked activity.
  • After remediation, confirm affected pages no longer expose unsafe script behavior.
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-30961 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-30961Attack 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
tinuzzTrackservertrackserver, 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.