LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45651: WordPress WP Attachments Plugin <= 5.0.11 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Marco Milesi WP Attachments allows Cross Site Request Forgery.This issue affects WP Attachments: from n/a through 5.0.11.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF flaw in the WordPress WP Attachments plugin. If an authenticated site user, likely an administrator, is tricked into an unwanted action, site attachment-related settings or data could be changed. The provided sources do not show active exploitation or a confirmed fixed version.

Executive priority

Treat as a routine but real WordPress hygiene issue. Prioritize public or business-critical sites using WP Attachments, especially where many administrators access the dashboard. It does not justify emergency response unless local evidence shows suspicious changes.

Technical view

CVE-2023-45651 is CWE-352 in Marco Milesi WP Attachments, reported for versions through 5.0.11. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required by the attacker, user interaction required, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the WP Attachments plugin installed in an affected version. The source bundle does not identify affected CPEs, hosting environments, or a confirmed fixed release, so asset inventory is required.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. CSRF typically depends on tricking an authenticated user into performing a state-changing action, so real-world risk rises where privileged WordPress users browse while logged in.

Researcher notes

Evidence is sparse. The CVE description says WP Attachments through 5.0.11, while the Patchstack reference URL names 5.0.6. No exploit details, patch version, or mitigation specifics are provided in the bundle. Validate against current vendor or Patchstack guidance before closing remediation.

Mitigation direction

  • Inventory WordPress sites for the WP Attachments plugin and installed version.
  • Check vendor, WordPress plugin, and Patchstack guidance for a fixed release.
  • Update the plugin if a vendor-confirmed fixed version is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit WordPress administrator sessions to trusted devices and workflows.

Validation and detection

  • Confirm whether WP Attachments is installed on each WordPress property.
  • Record exact plugin versions and compare against the CVE affected range through 5.0.11.
  • Review vendor and Patchstack entries for corrected affected-version or fix details.
  • Check WordPress administrative audit history for unexpected attachment-related changes.
  • Verify security monitoring covers privileged WordPress account activity.
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-45651 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-45651Attack 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
Marco MilesiWP Attachmentswp-attachments, 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.