LiveActive security incident?Get immediate response
CVE Record

CVE-2024-54300: WordPress AutoWP plugin <= 2.0.8 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Basar Ventures AutoWP autowp-ai-content-writer-rewriter allows Cross Site Request Forgery.This issue affects AutoWP: from n/a through <= 2.0.8.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-54300 is a CSRF issue in the WordPress AutoWP plugin up to version 2.0.8. An attacker may be able to trick a logged-in site user into causing an unintended low-impact change. The sources do not show data theft, outage impact, or active exploitation.

Executive priority

Treat this as a routine but real WordPress plugin hygiene issue. Prioritize public sites where AutoWP is installed and administrator sessions are common, but it does not currently justify emergency response absent evidence of exploitation or broader impact.

Technical view

The issue is CWE-352 in Basar Ventures AutoWP autowp-ai-content-writer-rewriter through 2.0.8. CVSS 3.1 score 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 sites with the AutoWP plugin installed at version 2.0.8 or earlier. Sites without this plugin, or with a version not in the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not identify known exploitation, and CISA KEV status is false. Exploitation would require user interaction, consistent with the CVSS vector and CSRF class, but the sources do not describe the vulnerable action or provide exploit details.

Researcher notes

Evidence is sparse. The sources identify the vulnerability class, affected plugin, affected version ceiling, CVSS vector, and Patchstack advisory, but not the exact endpoint, vulnerable action, exploit maturity, or fixed version. Avoid assuming impact beyond low integrity change.

Mitigation direction

  • Inventory WordPress sites for the AutoWP plugin and version.
  • Check vendor and Patchstack guidance for a fixed release or official workaround.
  • Update the plugin if a fixed version is available from trusted sources.
  • Disable or remove AutoWP where it is not business-critical.
  • Review recent site changes for unexpected content or settings modifications.

Validation and detection

  • Confirm whether autowp-ai-content-writer-rewriter is installed on each WordPress site.
  • Verify installed plugin versions against the affected range: through 2.0.8.
  • Review the CVE and Patchstack entries for any updated vendor guidance.
  • Check administrative logs for unexpected AutoWP-related changes.
  • Document systems confirmed unaffected because the plugin is absent.
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-2024-54300 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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.4Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-54300Attack 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

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Basar VenturesAutoWPautowp-ai-content-writer-rewriter, 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.