LiveActive security incident?Get immediate response
CVE Record

CVE-2024-37493: WordPress Posterity theme <= 3.3 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in sonalsinha21 Posterity posterity allows Cross Site Request Forgery.This issue affects Posterity: from n/a through <= 3.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-37493 is a CSRF issue in the WordPress Posterity theme through version 3.3. It could let an attacker trick a logged-in user into performing an unintended action. The cited CVSS score is 4.3, so business urgency is moderate and depends on whether the theme is deployed.

Executive priority

Treat as a moderate website hygiene issue. Prioritize externally facing WordPress sites, especially those with frequent admin activity, but do not escalate as an emergency without evidence of exposure or exploitation.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in sonalsinha21 Posterity for WordPress, affecting versions through 3.3. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, indicating network reachability, required user interaction, and limited integrity impact.

Likely exposure

Exposure is limited to WordPress sites with the Posterity theme installed or active at version 3.3 or earlier. The source bundle does not identify specific vulnerable endpoints, required roles, or a fixed version.

Exploitation context

The CVE is not listed as CISA KEV, and the provided sources do not claim active exploitation. Exploitation would require a targeted logged-in user to interact with attacker-controlled content or a malicious link.

Researcher notes

Available evidence confirms the vulnerability class, product, affected range, CVSS score, and Patchstack entry. It does not provide endpoint details, proof-of-concept status, exploit telemetry, or an official fixed version in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for Posterity theme version 3.3 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or official remediation.
  • Upgrade only to a vendor-confirmed fixed version if one is available.
  • If no fix is available, replace or disable the theme where business risk allows.

Validation and detection

  • Confirm whether Posterity is installed or active on each WordPress instance.
  • Record the exact theme version and compare it to the affected range through 3.3.
  • Review administrator change history for unexpected configuration or content modifications.
  • Track remediation status against CVE-2024-37493 in vulnerability management records.
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-37493 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-37493Attack 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
sonalsinha21Posterityposterity, 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.