CVE-2023-36519
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 wpthemego SW Product Bundles allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SW Product Bundles: from n/a through 2.0.15.
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 confidenceThe wpthemego SW Product Bundles WordPress plugin versions up to 2.0.15 contain a missing authorization vulnerability where the plugin fails to properly enforce access control checks. This allows unauthenticated or unauthorized users to access functionality that should be restricted to authenticated users with proper privileges, likely due to incorrectly configured security levels in the plugin's access control implementation.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify SW Product Bundles plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'SW Product Bundles' by wpthemego, or check the plugins directory for the wpthemego/sw-product-bundles folderAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin Plugins list, click on the plugin details for SW Product Bundles and note the version number displayed, or check the plugin's main PHP file for the Version header commentAffected if Version is 2.0.15 or lower (any version up to and including 2.0.15)
-
Test unauthenticated access to plugin admin functionsAttempt to access common plugin admin URLs directly without logging in, such as /wp-admin/admin.php?page=sw-product-bundles or similar plugin-specific admin endpointsAffected if Access is granted without authentication or without proper WordPress capability checks (user roles/permissions)
-
Review server-level access controlsCheck .htaccess or server configuration for any rules restricting access to the plugin's admin functionality, or inspect WordPress capability checks in the plugin code if accessibleAffected if No server-level restrictions exist AND the plugin lacks proper wp_ajax or admin_init capability checks
A user is affected if the SW Product Bundles plugin version 2.0.15 or lower is installed AND unauthenticated or unauthorized users can access plugin admin functionality that should require authentication and proper WordPress capabilities.
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 the SW Product Bundles plugin to the latest version once available, or disable the plugin until a patch is released. If immediate remediation is required, review and restrict access to the plugin's admin functions at the server level or through WordPress capability checks.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36519 — 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-36519 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