dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-36526

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
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
Missing Authorization vulnerability in Inqsys Technology Duplicate Post Page Menu & Custom Post Type allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Duplicate Post Page Menu & Custom Post Type: from n/a through 2.4.1.

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 confidence

This is a missing authorization (broken access control) vulnerability in the 'Duplicate Post Page Menu & Custom Post Type' WordPress plugin affecting versions up to 2.4.1. The plugin fails to properly validate user permissions before allowing duplication operations, enabling authenticated users to potentially duplicate content beyond their authorized scope.

MitigationUpdate the plugin to the latest version which includes proper authorization checks. Review user role capabilities and implement principle of least privilege for duplication functionality.

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
None
Integrity
Low
Availability
Low

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

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. Check if the plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Duplicate Post Page Menu & Custom Post Type'. Note the version number displayed.
    Affected if The plugin is installed and the version shown is 2.4.1 or lower
  2. Verify the plugin version via file system
    Access the plugin directory at wp-content/plugins/duplicate-post-page-menu-custom-post-type/ and open the readme.txt file or the main plugin PHP file to confirm the exact version number.
    Affected if The version retrieved from files is 2.4.1 or lower
  3. Confirm the plugin duplication feature is active
    Check if the duplication functionality is accessible by looking for 'Duplicate' options on posts, pages, or custom post types in the WordPress admin. This can be confirmed by viewing the post list table or using the plugin's settings page.
    Affected if The duplication options are visible and functional for any authenticated user role
  4. Test authorization on duplication operations
    Use a low-privileged user account (e.g., Subscriber or Contributor) to attempt duplicating content they did not create. Observe if the duplication succeeds without proper permission validation.
    Affected if Users can duplicate content beyond their authorized scope, indicating the broken access control is present

The environment is affected if the plugin version is 2.4.1 or lower and any authenticated user can duplicate content they should not have permission to duplicate.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version which includes proper authorization checks. Review user role capabilities and implement principle of least privilege for duplication functionality.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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