LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54685: WordPress SureDash Plugin <= 1.1.0 - Sensitive Data Exposure Vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in Brainstorm Force SureDash suredash allows Retrieve Embedded Sensitive Data.This issue affects SureDash: from n/a through <= 1.1.0.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-54685 is a medium-severity data exposure issue in the WordPress SureDash plugin through version 1.1.0. A logged-in low-privilege user may be able to retrieve sensitive data embedded in sent information. The main business risk is confidentiality loss, not site takeover or outage based on the provided sources.

Executive priority

Treat this as a confidentiality-focused medium priority. It should be addressed during normal vulnerability remediation, faster for public WordPress sites with customer, member, or internal data and many authenticated users.

Technical view

The CVE describes CWE-201, insertion of sensitive information into sent data, affecting Brainstorm Force SureDash for WordPress through <= 1.1.0. CVSS 3.1 is 6.5: network-reachable, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure appears limited to WordPress sites running SureDash versions up to and including 1.1.0, especially where low-privilege user accounts exist. Sources do not identify affected configurations, exact data types exposed, or a fixed version.

Exploitation context

The source bundle does not report active exploitation, KEV listing, public exploit code, or exploitation in the wild. The CVSS vector indicates exploitation requires network access and a low-privilege authenticated account, with no victim interaction required.

Researcher notes

Available evidence is sparse. The CVE and Patchstack entry identify the weakness class, affected plugin, affected version range, and CVSS vector, but not the vulnerable endpoint, exposed fields, fixed version, or confirmed exploitation status.

Mitigation direction

  • Inventory WordPress sites for the SureDash plugin and recorded versions.
  • Prioritize upgrades or vendor guidance for SureDash <= 1.1.0.
  • Restrict low-privilege account creation and access on affected sites.
  • Disable or remove the plugin if exposure is unacceptable and no fix is available.
  • Review logs for unusual access by low-privilege accounts.

Validation and detection

  • Confirm whether SureDash is installed on each WordPress site.
  • Record installed plugin versions and flag <= 1.1.0.
  • Check vendor and Patchstack pages for fixed-version guidance.
  • Review user roles and remove unnecessary low-privilege accounts.
  • Assess whether sensitive data could be embedded in plugin responses.
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-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-54685 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:N/S:U/C:H/I:N/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
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:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
Brainstorm ForceSureDashsuredash, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.