LiveActive security incident?Get immediate response
CVE Record

CVE-2016-20074: WordPress Lazy Content Slider Plugin 3.4 CSRF

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
4

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-2016-20074 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.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA: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.

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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:LVulnCheck
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2016-20074Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
leethompsonLazy Content Slider Plugin3.4Listed
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.