dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0727

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-14
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 and Accordion Slider plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.4.5. This is due to the plugin not properly verifying that a user is authorized to perform an action in the 'wp_aas_save_attachment_data' and 'wp_aas_get_attachment_edit_form' functions. This makes it possible for authenticated attackers, with contributor level access and above, to read and modify attachment metadata including file paths, titles, captions, alt text, and custom links for any attachment on the site.

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 and Accordion Slider WordPress plugin lacks proper authorization checks in the wp_aas_save_attachment_data and wp_aas_get_attachment_edit_form functions. This allows any authenticated user with contributor-level access or higher to read and modify metadata (file paths, titles, captions, alt text, custom links) for any attachment on the site, representing an Insecure Direct Object Reference (IDOR) vulnerability.

MitigationUpgrade to version 1.4.6 or later which includes proper capability checks and nonce verification for the affected functions. If immediate patching is not possible, disable the plugin until a patch can be applied.

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. Locate the Accordion and Accordion Slider plugin
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/accordion-accordion-slider/ directory via file system
    Affected if Plugin is present and active in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress admin, view the plugin details page to see the version number, or check the main plugin PHP file for the Version header comment
    Affected if Version is lower than 1.4.6 (or version cannot be determined and plugin is active)
  3. Verify contributor-level or higher user accounts exist
    Navigate to Users > All Users in WordPress admin and review user roles; contributor role users have edit_posts capability
    Affected if At least one user account has contributor, author, editor, or administrator role
  4. Confirm the vulnerable AJAX endpoints are accessible
    Check if the plugin registers wp_aas_save_attachment_data and wp_aas_get_attachment_edit_form actions via add_action('wp_ajax_wp_aas_...'); inspect plugin source for these function definitions
    Affected if These functions exist without proper capability checks (for example, missing current_user_can('edit_others_posts') or similar authorization)

The environment is affected if the Accordion and Accordion Slider plugin is installed with a version below 1.4.6 and the site has any authenticated users with contributor-level access or higher.

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

Upgrade to version 1.4.6 or later which includes proper capability checks and nonce verification for the affected functions. If immediate patching is not possible, disable the plugin until a patch can be applied.

Recommended fix Moderate confidence

Latest version of Accordion and Accordion Slider plugin (version greater than 1.4.5)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Accordion and Accordion Slider' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is greater than 1.4.5
  6. 6. Test that attachment metadata functions work correctly for authorized users only

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0727 — 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-2026-0727 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