LiveActive security incident?Get immediate response
CVE Record

CVE-2023-7048: My Sticky Bar <= 2.6.6 - Cross-Site Request Forgery to Sensitive Information Exposure

The My Sticky Bar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.6. This is due to missing or incorrect nonce validation in mystickymenu-contact-leads.php. This makes it possible for unauthenticated attackers to trigger the export of a CSV file containing contact leads via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Because the CSV file is exported to a public location, it can be downloaded during a very short window of time before it is automatically deleted by the export function.

LowCVSS 3.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

A WordPress site using My Sticky Bar up to version 2.6.6 could expose contact lead data if an administrator is tricked into triggering a forged request. The exported CSV is briefly placed in a public location before automatic deletion, limiting but not removing confidentiality risk.

Executive priority

Treat this as a low-priority confidentiality issue unless the site stores sensitive leads or has many WordPress administrators. Remediate through normal plugin maintenance, but do not defer indefinitely on public-facing lead collection sites.

Technical view

CVE-2023-7048 is a CSRF issue in mystickymenu-contact-leads.php caused by missing or incorrect nonce validation. An unauthenticated attacker needs administrator interaction to trigger contact-lead CSV export. Impact is limited information disclosure; no integrity or availability impact is described.

Likely exposure

Exposure is limited to WordPress installations running My Sticky Bar, formerly myStickymenu, in versions up to and including 2.6.6 with contact leads present.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. Successful abuse requires tricking a site administrator into an action, then retrieving the CSV during a short public availability window.

Researcher notes

The main uncertainty is patch mapping: the bundle cites a WordPress Trac changeset but does not explicitly name a fixed version. Validation should stay focused on version inventory, CSRF nonce coverage, and whether public CSV export behavior remains reachable.

Mitigation direction

  • Inventory WordPress sites using My Sticky Bar or myStickymenu.
  • Check installed plugin versions and prioritize versions up to 2.6.6.
  • Review vendor or WordPress plugin guidance for the fixed release.
  • Apply the vendor-supported update when available.
  • Restrict administrator browsing and link handling on production WordPress sessions.
  • Review exposed contact lead data retention and collection necessity.

Validation and detection

  • Confirm whether My Sticky Bar is installed on each WordPress site.
  • Record plugin version and compare it to 2.6.6 or earlier.
  • Review plugin changelog or WordPress Trac changeset 3016780.
  • Check whether contact lead exports or public CSV artifacts are logged.
  • Verify administrators have CSRF-aware operational procedures.
Prepared
Confidence
high
Sources
4

Public sources used

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-352: 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-2023-7048 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
Low
CVSS
3.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/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
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
3.1CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N1.61.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.1Low
CVSS 3.1 vector shape for CVE-2023-7048Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
premioMy Sticky Bar – Floating Notification Bar & Sticky Header (formerly myStickymenu)0unaffected
Weakness

CWE details

CWE-352

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs