LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52216: WordPress JS & CSS Script Optimizer Plugin <= 0.3.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Yevhen Kotelnytskyi JS & CSS Script Optimizer.This issue affects JS & CSS Script Optimizer: from n/a through 0.3.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52216 is a CSRF flaw in the WordPress JS & CSS Script Optimizer plugin through version 0.3.3. An attacker could try to trick a logged-in user into causing an unintended plugin action. The published impact is limited integrity loss, not data theft or outage.

Executive priority

Moderate priority. Address during WordPress plugin maintenance or faster for high-value public sites with many administrators. Current sources support integrity risk, but not active exploitation or critical business disruption.

Technical view

The issue is classified as CWE-352 Cross-Site Request Forgery in Yevhen Kotelnytskyi JS & CSS Script Optimizer for WordPress through 0.3.3. CVSS 3.1 is 4.3, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, indicating network reachability, required user interaction, and low integrity impact.

Likely exposure

Exposure appears limited to WordPress deployments running the named plugin at versions through 0.3.3. Organizations not using JS & CSS Script Optimizer are not affected based on the provided sources.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. CSRF generally depends on user interaction, and the CVSS vector confirms user interaction is required. No exploit details are provided in the bundle.

Researcher notes

The bundle does not identify the vulnerable endpoint, exact action, exploit prerequisites beyond user interaction, or fixed version. Validate exposure through inventory and vendor advisory review rather than offensive reproduction.

Mitigation direction

  • Inventory WordPress sites for the js-css-script-optimizer plugin.
  • If installed through 0.3.3, check Patchstack or vendor guidance for a fixed release.
  • Disable or remove the plugin if it is not required.
  • Limit WordPress administrator exposure and keep admin sessions separated from general browsing.
  • Monitor WordPress audit logs for unexpected plugin setting changes.

Validation and detection

  • Confirm whether JS & CSS Script Optimizer is installed on each WordPress site.
  • Record the installed plugin version and compare it with 0.3.3.
  • Review plugin change history or vendor notes for a patched version.
  • Check administrative logs for unexpected optimizer configuration changes.
  • Confirm compensating controls around WordPress admin access and session hygiene.
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-2023-52216 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-52216Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Products and packages named in the record

VendorProductVersion / packageStatus
Yevhen KotelnytskyiJS & CSS Script Optimizerjs-css-script-optimizer, n/aunaffected
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.