LiveActive security incident?Get immediate response
CVE Record

CVE-2023-32104: WordPress MyCurator Content Curation Plugin <= 3.74 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Mark Tilly MyCurator Content Curation plugin <= 3.74 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the WordPress MyCurator Content Curation plugin through version 3.74. It is a CSRF flaw, meaning an attacker may be able to trick a logged-in user into making an unintended change. The published impact is limited to integrity; no confidentiality or availability impact is reported.

Executive priority

Treat this as a routine but real WordPress plugin hygiene issue. It is not KEV-listed and has limited integrity impact, but exposed content-management sites should be checked and remediated during the next normal security maintenance cycle.

Technical view

CVE-2023-32104 is CWE-352 Cross-Site Request Forgery in Mark Tilly MyCurator Content Curation for WordPress, reported for versions <= 3.74. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required, user interaction required, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites that have MyCurator Content Curation installed at version 3.74 or earlier. Risk depends on whether privileged or content-management users are logged in and can be induced to interact with attacker-controlled content.

Exploitation context

The bundle does not identify active exploitation, and CISA KEV status is false. The vulnerability requires user interaction, which lowers urgency compared with unauthenticated direct compromise, but CSRF can still create unwanted site or plugin state changes.

Researcher notes

Evidence is narrow: the bundle provides CVE metadata and a Patchstack advisory reference, but no detailed affected-version matrix, exploit narrative, or explicit remediation text. Avoid claiming exploitation or a specific fixed version unless confirmed from vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the MyCurator Content Curation plugin.
  • Identify any installations running version 3.74 or earlier.
  • Check official plugin, vendor, or Patchstack guidance for a fixed release.
  • Disable or remove the plugin where it is unused or cannot be safely updated.
  • Prioritize sites where high-privilege users regularly access WordPress admin sessions.

Validation and detection

  • Confirm plugin presence and exact version from WordPress administration or asset inventory.
  • Review change logs or vendor advisories before assuming a version is fixed.
  • Check whether affected sites rely on MyCurator workflows or admin actions.
  • Verify compensating controls around WordPress admin access and session hygiene.
  • Document whether each site is vulnerable, updated, removed, or accepted as risk.
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-32104 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-32104Attack 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
Mark TillyMyCurator Content Curationmycurator, 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.