LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24708: WordPress W3SPEEDSTER Plugin <= 7.19 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in W3speedster W3SPEEDSTER.This issue affects W3SPEEDSTER: from n/a through 7.19.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24708 is a CSRF issue in the WordPress W3SPEEDSTER plugin through version 7.19. A successful attack could cause an authenticated user to perform an unintended plugin action, creating limited integrity impact. The sources do not identify data theft, service outage, active exploitation, or a named fixed version.

Executive priority

Treat this as a moderate WordPress hygiene issue, not an emergency based on current evidence. Prioritize internet-facing business sites using W3SPEEDSTER, especially where plugin configuration changes could affect performance, availability indirectly, or customer-facing behavior.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in W3speedster W3SPEEDSTER, package w3speedster-wp, affecting versions through 7.19. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress environments running W3SPEEDSTER version 7.19 or earlier. The source bundle does not list CPEs, exact vulnerable actions, hosting assumptions, or affected WordPress roles, so confirm exposure directly from plugin inventory and vendor advisories.

Exploitation context

The CVE is not listed as KEV in the source bundle, and the provided sources do not claim active exploitation. The CVSS vector indicates exploitation requires user interaction and can affect integrity, but the public details provided are not enough to describe a precise attack path.

Researcher notes

Public evidence is sparse. The sources identify CSRF, affected versions through 7.19, and CVSS 4.3, but do not provide endpoint details, required victim role, proof of exploitation, or a named fixed version. Avoid assuming broader impact without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for W3SPEEDSTER versions 7.19 or earlier.
  • Check Patchstack and vendor guidance for a fixed release or official mitigation.
  • Update the plugin if an official fixed version is available.
  • If no fix is available, consider disabling the plugin after business-impact review.
  • Prioritize sites where privileged WordPress users remain logged in frequently.

Validation and detection

  • Confirm installed W3SPEEDSTER versions against the affected range through 7.19.
  • Review plugin and WordPress admin logs for unexpected configuration changes.
  • Verify state-changing plugin actions use CSRF protection in non-production testing.
  • Recheck CVE and Patchstack entries for updated fix or exploitation details.
Prepared
Confidence
high
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-2024-24708 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-2024-24708Attack 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
W3speedsterW3SPEEDSTERw3speedster-wp, 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.