CVE-2023-46644
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 · uneditedMissing Authorization vulnerability in WP CTA PRO WordPress CTA allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WordPress CTA: from n/a through 1.5.8.
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 confidenceThis is a Missing Authorization vulnerability in the WP CTA PRO WordPress plugin. The plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels to perform actions they should not be authorized to perform. The vulnerability affects versions through 1.5.8.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP CTA PRO plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'WP CTA PRO' or 'WP Call To Action PRO' in the list. Also check if the plugin is activated.Affected if The plugin is installed and active in WordPress
-
Check installed plugin versionIn the Plugins list, click on the plugin to view details, or access the main plugin PHP file (typically in /wp-content/plugins/wp-cta-pro/ or similar) and check the plugin header for the Version field.Affected if The displayed version is 1.5.8 or any version lower than 1.5.8
-
Identify plugin security configurationNavigate to the plugin settings page in WordPress admin (usually under a menu item like 'WP CTA', 'Call to Action', or similar). Look for any security level, access control, role capability, or permission settings that control who can access or modify plugin features.Affected if A security level or role configuration exists and is set to allow access to users who should not have such access (this is the vulnerable misconfiguration)
-
Verify WordPress user roles affectedReview which WordPress user roles (Administrator, Editor, Author, Contributor, Subscriber) have access to plugin functions. Check if lower-privileged users can access features intended only for administrators.Affected if Users with roles below Administrator (such as Editor, Author, or Subscriber) can perform actions that should require higher privileges
You are affected if the WP CTA PRO plugin is active with version 1.5.8 or lower, and any WordPress user with limited privileges can access or modify plugin settings or perform actions they should not be authorized to perform.
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.
From vendor dataUpdate to the latest version of WP CTA PRO which should include proper authorization checks. If no update is available, review the plugin's code for missing capability checks and add proper authorization validation before sensitive operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46644 — 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-46644 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