dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-46632

HIGH · 7.1 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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 David Cramer My Shortcodes allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects My Shortcodes: from n/a through 2.3.

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

Missing authorization vulnerability in My Shortcodes plugin allows exploiting incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functionality, potentially enabling unauthorized users to perform actions outside their intended permission scope.

MitigationUpdate My Shortcodes to the latest patched version and review all access control configurations to ensure proper authorization checks are enforced on all sensitive operations.

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 checks

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

  1. Verify My Shortcodes plugin is installed
    Navigate to WordPress admin dashboard > Plugins and search for 'My Shortcodes' in the installed plugins list, or check the /wp-content/plugins/ directory for a my-shortcodes folder
    Affected if The plugin is installed and active
  2. Identify installed My Shortcodes version
    In WordPress admin, go to Plugins > Installed Plugins > My Shortcodes and note the version number displayed, or inspect the main plugin file header in /wp-content/plugins/my-shortcodes/my-shortcodes.php for the 'Version' tag
    Affected if The installed version is older than the patched version (any unpatched version may be vulnerable)
  3. Check for publicly accessible shortcode endpoints
    Visit your site homepage and view page source to identify any shortcodes loaded from My Shortcodes (common patterns: [my_shortcode], [msc], or custom shortcodes), then test if these are accessible to unauthenticated visitors by visiting the site in a private/incognito window
    Affected if The plugin exposes shortcodes or functionality that is accessible to unauthenticated or lower-privileged users
  4. Inspect user role and capability configuration
    Go to WordPress admin > Users > Roles (or use a role editor plugin) and review what capabilities are assigned to subscriber, contributor, and author roles related to My Shortcodes functionality
    Affected if Lower-privileged users (subscriber, contributor) have capabilities that should be restricted to administrators
  5. Check plugin settings for access control misconfiguration
    Navigate to My Shortcodes plugin settings page in WordPress admin (usually under Settings or a dedicated My Shortcodes menu) and review any access control, permission level, or user role configuration options
    Affected if Access control settings allow non-administrator users to access restricted plugin features

You are affected if the My Shortcodes plugin is installed with an unpatched version and exposes functionality accessible to users without proper authorization checks.

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 My Shortcodes to the latest patched version and review all access control configurations to ensure proper authorization checks are enforced on all sensitive operations.

Recommended fix Moderate confidence

My Shortcodes version 2.3.1 or later

  1. Update the My Shortcodes WordPress plugin to version 2.3.1 or later
  2. Verify the update was successful by checking the plugins page in WordPress admin
  3. Test that the shortcode functionality still works as expected after the update
  4. Confirm that unauthorized users can no longer access restricted functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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