WordPress Lazy Content Slider Plugin 3.4 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by crafting malicious HTML forms. Attackers can trick authenticated administrators into submitting POST requests to the plugin settings page via lzcs_admin.php to modify plugin configuration parameters like lzcs_color and lzcs_count.
Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress Lazy Content Slider Plugin version 3.4. A malicious site could cause an authenticated WordPress administrator to unintentionally change plugin settings. The direct impact is configuration tampering, not full site takeover based on the provided sources.
Executive priority
Treat this as a targeted website hygiene issue. It warrants prompt inventory and remediation on WordPress properties, but the provided evidence does not support emergency enterprise-wide escalation.
Technical view
The issue is CWE-352 cross-site request forgery in the plugin settings workflow, involving POST requests to lzcs_admin.php. Reported parameters include lzcs_color and lzcs_count. Sources identify version 3.4 as affected and provide a public exploit reference, but do not identify a vendor patch.
Likely exposure
Exposure is limited to WordPress sites running Lazy Content Slider Plugin 3.4, especially where administrators browse while authenticated. Sites not using this plugin or version are not indicated as affected by the source bundle.
Exploitation context
The CVE is not listed as KEV in the provided data. ExploitDB is cited, so public exploit information exists. The sources do not prove active exploitation in the wild.
Researcher notes
The strongest evidence is the CVE record, VulnCheck advisory, and ExploitDB reference. Available details describe settings modification through CSRF, but do not establish broader privilege escalation, data theft, patch status, or active exploitation.
Mitigation direction
Inventory WordPress sites for Lazy Content Slider Plugin 3.4.
Check vendor or project guidance for a fixed release or replacement.
Remove or disable the plugin if no maintained fix is available.
Limit WordPress administrator access to trusted users and managed devices.
Review administrator security awareness around malicious links and forms.
Validation and detection
Confirm whether Lazy Content Slider Plugin 3.4 is installed.
Review plugin configuration for unexpected recent changes.
Check web logs for suspicious plugin settings POST activity.
Verify whether any maintained version addresses CSRF protection.
Document compensating controls if the plugin must remain enabled.
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.
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.
2CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
2 official scores
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.
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.