LiveActive security incident?Get immediate response
CVE Record

CVE-2025-46508: WordPress Advanced lazy load plugin <= 1.6.0 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in kasonzhao Advanced lazy load advanced-lazy-load allows Stored XSS.This issue affects Advanced lazy load: from n/a through <= 1.6.0.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress Advanced lazy load plugin through version 1.6.0. A successful CSRF attack could cause stored cross-site scripting, meaning malicious script could be saved into the site and later run in visitors' browsers. The sources do not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat this as a high-priority WordPress plugin exposure. Prioritize public-facing sites and sites with privileged content editors, because stored XSS can affect visitors and administrators even without confirmed exploitation.

Technical view

CVE-2025-46508 is a CWE-352 CSRF issue in kasonzhao Advanced lazy load, package advanced-lazy-load, reported as allowing stored XSS through version 1.6.0. CVSS 3.1 is 7.1 high: network accessible, low complexity, no attacker privileges, user interaction required, and changed scope.

Likely exposure

Exposure is limited to WordPress sites running the Advanced lazy load plugin, especially versions up to and including 1.6.0. The bundle does not identify other affected products or a fixed version.

Exploitation context

The CVE is not marked KEV, and the supplied sources do not confirm active exploitation. The attack requires user interaction, consistent with CSRF, and may result in stored XSS if a targeted user is induced into the vulnerable action.

Researcher notes

Evidence is sufficient for vulnerability classification and affected plugin range, but incomplete on exploit maturity and fixed release details. Avoid assuming active exploitation or a patch version unless confirmed by vendor or Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the advanced-lazy-load plugin and installed version.
  • Check Patchstack and vendor guidance for a fixed version or official mitigation.
  • Disable or remove the plugin if no safe vendor-supported version is available.
  • Limit administrative access and reinforce anti-phishing controls for WordPress users.
  • Review web application firewall or virtual patching options from trusted providers.

Validation and detection

  • Confirm whether Advanced lazy load is installed on each WordPress site.
  • Flag installed versions less than or equal to 1.6.0 as potentially affected.
  • Review recent plugin settings or content changes for unexpected script-like content.
  • Check logs for suspicious authenticated actions around plugin configuration.
  • Verify remediation by confirming plugin removal, replacement, or vendor-documented fixed version.
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-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-2025-46508 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-46508Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
kasonzhaoAdvanced lazy loadadvanced-lazy-load, 0unaffected
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.