Skip to main content

Sitemovr CVE-2026-41563

| EUVDEUVD-2026-92958 HIGH
Insertion of Sensitive Information Into Sent Data (CWE-201)
2026-10-06 Patchstack GHSA-45f6-r7hw-m3jq
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site running Sitemovr ≤1.0.1
  2. Exploit
    Send unauthenticated HTTP request to plugin endpoint
  3. Impact
    Receive and harvest exposed sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
Exploitation Conditions

Exploitation requires only network access to a WordPress site running the Sitemovr plugin at version 1.0.1 or earlier; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, user interaction, or non-default configuration is indicated, so default installs appear exposed. The primary limiting factor is deployment: the flaw only affects sites that have this specific, obscure plugin installed and not updated past 1.0.1. Note the advisory does not specify the exact exposed data or endpoint, so defenders cannot scope precisely what information is leaked without the vendor/Patchstack detail.

Impact

Signals are consistent but thin. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity flaw requiring no privileges or user interaction, which maps cleanly to the 'Unauthenticated Sensitive Data Exposure' description and CWE-201 - so the 7.5 score is credible for a confidentiality-only issue (C:H/I:N/A:N). However, the decisive real-world signals are MISSING, not conflicting: no EPSS probability, no CISA KEV listing, and no public POC were provided, and no SSVC decision data was supplied. There is 'no public exploit identified at time of analysis.' The net effect is a genuinely remote, trivially triggerable disclosure bug, but confined to an obscure WordPress plugin, so despite the HIGH severity the practical priority is moderate and driven almost entirely by deployment footprint rather than by any evidence of exploitation. Treat the 7.5 as a theoretical-ease score, not an indicator of active threat.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted HTTP request to a WordPress site running Sitemovr 1.0.1 or earlier and receives sensitive information that the plugin discloses without access control. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no login, user interaction, or special timing is needed - a single request against a vulnerable install suffices. No public proof-of-concept was provided in the intelligence.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Unauthenticated sensitive data exposure in the Sitemovr WordPress plugin versions 1.0.1 and earlier allows remote attackers to retrieve undisclosed sensitive information from affected sites without authentication, user interaction, or non-default configuration, per the CVSS vector (7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Exploitation is limited mainly by deployment: only WordPress sites that use this obscure plugin and have not updated past 1.0.1 are exposed, and the Patchstack advisory does not specify exactly which data or endpoint leaks. No public exploit code was identified at time of analysis, and the independent assessment rates the available signals as consistent but thin.

RemediationAI

No exact fixed version or vendor-released patch is specified in the provided data, so verify the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/sitemovr/vulnerability/wordpress-sitemovr-plugin-1-0-1-sensitive-data-exposure-vulnerability?_s_id=cve for update guidance and upgrade to any version later than 1.0.1 if one is available. If no patched version exists, the most effective mitigation is to disable and remove the Sitemovr plugin, since eliminating an obscure plugin removes the exposure entirely (trade-off: loss of its site functionality). If removal is not possible, restrict access to the site and to Sitemovr-related endpoints using WAF or reverse-proxy rules, but note the advisory does not identify the exact leaking endpoint, so such rules may be incomplete and could block legitimate plugin requests. Additionally, monitor access logs for unauthenticated requests to Sitemovr plugin paths and review responses for unexpected sensitive data as a compensating detective control.

Affected VersionsENISA

Sitemovr n/a ≤1.0.1

Affected Packages

euvd sitemovr no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is tracked as CWE-201 (Insertion of Sensitive Information Into Sent Data), meaning the plugin transmits sensitive information in a response or outbound data flow without adequate protection or authorization checks. The affected technology is the Sitemovr WordPress plugin, a PHP-based component running inside a WordPress installation; the CPE string cpe:2.3:a:dawer_drew:sitemovr:*:*:*:*:*:*:*:* identifies the Dawer Drew Sitemovr product, while the description scopes vulnerable versions to 1.0.1 and earlier. The CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N indicates a remotely reachable, low-complexity flaw requiring no privileges or user interaction, with high confidentiality impact but no integrity or availability impact. The advisory does not disclose the exact endpoint, parameter, or sensitive field involved, so the precise sink cannot be confirmed from the provided data.

Know when Sitemovr gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network-reachable disclosure (AV:N/PR:N/UI:N) per description; confidentiality-only impact (C:H, I:N, A:N) consistent with CWE-201.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Unauthenticated Sensitive Data Exposure in Sitemovr <= 1.0.1 versions.

Executive ViewAI

Why It Matters

The Sitemovr WordPress plugin (versions 1.0.1 and earlier) contains an unauthenticated sensitive data exposure vulnerability (CVE-2026-41563) that could allow remote attackers to retrieve confidential information from affected websites. Organizations using this plugin face potential data leakage that may violate privacy regulations or expose proprietary content, though exploitation is currently limited by the plugin's niche adoption and the absence of public exploit code. Leadership should prioritize identifying and mitigating affected WordPress instances to prevent potential reputational and compliance damage.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the Sitemovr plugin (versions 1.0.1 and earlier) where possible, implementing WAF rules to block unauthenticated access to plugin endpoints, monitoring web server and application logs for suspicious data access patterns, and restricting network access to affected WordPress sites.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Rare
obscure third-party WordPress plugin, negligible install footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy