LiveActive security incident?Get immediate response
CVE Record

CVE-2024-33679: WordPress FameTheme Demo Importer plugin <= 1.1.5 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in FameThemes FameTheme Demo Importer.This issue affects FameTheme Demo Importer: from n/a through 1.1.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress FameTheme Demo Importer plugin through version 1.1.5. An attacker could try to trick an authenticated site user into triggering an unintended plugin action. The cited severity is medium, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat as a routine but time-bound WordPress plugin remediation item. It is not presented as actively exploited, but exposed sites should inventory and remove or update the plugin because CSRF can cause unauthorized changes through trusted users.

Technical view

CVE-2024-33679 is CWE-352 affecting FameThemes FameTheme Demo Importer, package famethemes-demo-importer, through 1.1.5. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, integrity impact low.

Likely exposure

Exposure is limited to WordPress sites that have FameTheme Demo Importer installed at version 1.1.5 or earlier. The bundle does not identify affected themes, endpoint names, required victim role, or a fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation would require user interaction, consistent with CSRF, likely involving a logged-in WordPress user being induced to perform an unintended action.

Researcher notes

Evidence is concise: CVE, CVSS, CWE-352, affected plugin through 1.1.5, and Patchstack entry. The bundle does not provide vulnerable endpoints, proof of concept, fixed version, or exploit telemetry, so validation should stay focused on version exposure and vendor updates.

Mitigation direction

  • Inventory WordPress sites for the famethemes-demo-importer plugin.
  • Upgrade if vendor or Patchstack guidance identifies a fixed version.
  • Disable or remove the plugin if it is not operationally required.
  • Limit administrative browsing from active WordPress sessions.
  • Monitor vendor, CVE, and Patchstack pages for updated remediation details.

Validation and detection

  • Confirm whether FameTheme Demo Importer is installed on each WordPress site.
  • Record installed plugin versions and flag 1.1.5 or earlier.
  • Check WordPress admin updates and vendor sources for remediation availability.
  • Review recent administrative changes for unexpected demo-importer activity.
  • Verify compensating controls after disabling or removing the plugin.
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-33679 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-33679Attack 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
FameThemesFameTheme Demo Importerfamethemes-demo-importer, 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.