LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6499: lasTunes <= 3.6.1 - Settings Update via CSRF

The lasTunes WordPress plugin through 3.6.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects the lasTunes WordPress plugin through version 3.6.1. A logged-in administrator could be tricked into changing plugin settings, potentially saving malicious script content. Business risk is mainly site integrity, admin-session abuse, and possible visitor or administrator browser impact if stored script runs.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Prioritize internet-facing or business-critical sites, but do not treat it as emergency active exploitation based on the provided sources.

Technical view

The issue is missing CSRF validation in some lasTunes settings paths, combined with missing sanitization and escaping. The reported outcome is stored XSS inserted through a CSRF-triggered settings update. CVSS 3.1 is 5.4 medium with user interaction required and changed scope.

Likely exposure

Exposure appears limited to WordPress sites running the lasTunes plugin through 3.6.1, especially where administrators remain logged in while browsing attacker-controlled content.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. WPScan is tagged as an exploit reference, but the provided evidence does not establish in-the-wild exploitation.

Researcher notes

Evidence supports CWE-352 CSRF with stored XSS impact caused by missing CSRF checks, sanitization, and escaping. Patch availability is not named in the bundle, so remediation should be tied to vendor or WPScan guidance rather than assumed.

Mitigation direction

  • Inventory WordPress sites for the lasTunes plugin and version.
  • Check vendor or WPScan guidance for a fixed release or official mitigation.
  • Disable or remove lasTunes where business use is not required.
  • Limit WordPress administrator access to trusted users and hardened workstations.
  • Review site content and plugin settings for unexpected script content.

Validation and detection

  • Confirm whether lasTunes is installed and version is through 3.6.1.
  • Review plugin settings for untrusted or unexpected saved values.
  • Check WordPress admin activity around plugin settings changes.
  • Monitor security feeds for vendor fix details and updated WPScan guidance.
Prepared
Confidence
medium
Sources
3

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-6499 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
5.4 (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: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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-6499Attack 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: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
UnknownlasTunes0affected
Weakness

CWE details

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.