dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1641

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Accordion plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the 'accordions_duplicate_post_as_draft' function in all versions up to, and including, 2.2.96. This makes it possible for authenticated attackers, with contributor access and above, to duplicate arbitrary posts, allowing access to the contents of password-protected posts.

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 · high confidence

The Accordion WordPress plugin has a broken access control vulnerability in the 'accordions_duplicate_post_as_draft' function which lacks capability checks. This allows any authenticated user with contributor-level access or higher to duplicate arbitrary posts, including password-protected posts, leading to unauthorized data access and modification.

MitigationUpdate the Accordion plugin to version 2.2.97 or later which includes proper capability checks on the affected function to restrict the duplicate functionality to authorized users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Accordion plugin is installed
    Check your WordPress plugins directory (wp-content/plugins/) for the 'accordions' or 'accordion' plugin folder, or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The Accordion plugin is present in the installation
  2. Check installed plugin version
    Open the plugin's main PHP file or readme.txt in the accordion plugin directory and locate the version number declared in the plugin header comment
    Affected if Version is 2.2.96 or lower (versions below 2.2.97 are vulnerable)
  3. Identify the vulnerable function
    Search the plugin PHP files for the function named 'accordions_duplicate_post_as_draft' - this function should exist in the affected version
    Affected if The function 'accordions_duplicate_post_as_draft' is present and lacks capability checks
  4. Verify user role configuration
    In WordPress admin, go to Users > All Users and review which users have the Contributor role or higher
    Affected if Any user account with Contributor, Author, Editor, or Administrator role exists in the system

Your environment is affected if the Accordion plugin version is 2.2.96 or lower, the vulnerable duplicate function exists, and any authenticated user with contributor-level access or higher is present in WordPress.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Accordion plugin to version 2.2.97 or later which includes proper capability checks on the affected function to restrict the duplicate functionality to authorized users only.

Recommended fix Moderate confidence

Latest version of the Accordion plugin (version higher than 2.2.96)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the 'Accordion' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 2.2.96
  6. 6. Test that the duplicate post functionality works correctly with appropriate user permissions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1641 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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