Wp AttachmentsWordPress extension · Marcomilesi
CVE-2023-45651
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Attachments WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying attachments or settings) by crafting malicious requests that the victim's browser automatically submits.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp AttachmentsWordPress extension
<= 5.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if WP Attachments plugin is installedCheck the WordPress plugins directory or admin panel for the Marcomilesi Wp Attachments pluginAffected if The plugin is present in the WordPress installation
-
Determine the installed versionInspect the plugin header in wp-content/plugins/wp-attachments/plugin.php or view the version in the WordPress plugin admin listAffected if The version number is 5.0.6 or lower
-
Verify plugin is activeCheck the WordPress admin under Plugins > Installed Plugins to confirm the plugin status is ActiveAffected if The plugin is activated and accessible to administrators
-
Confirm state-changing functionality existsNavigate to the WP Attachments settings page in the WordPress admin dashboardAffected if The plugin settings or attachment management interface is accessible to authenticated administrators
-
Check for CSRF protection on formsInspect page source of WP Attachments admin pages to look for nonce fields (wp_create_nonce, wp_verify_nonce, or _wpnonce) in forms that modify settings or attachmentsAffected if Forms handling attachment or setting modifications lack anti-CSRF nonce tokens
The environment is affected if Marcomilesi Wp Attachments plugin is installed, active, and running at version 5.0.6 or lower, exposing admin-configurable settings to CSRF attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions within the plugin, and validate the Origin/Referer headers on POST requests to ensure they originate from the legitimate site.
WP Attachments version 5.0.12 or later
- 1. Backup your WordPress site before making any changes
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Locate the WP Attachments plugin in the list
- 4. Click 'Update now' if an update is available, or manually download version 5.0.12 or later from the WordPress plugin repository
- 5. Verify the update was successful by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Attachments
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45651 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data