CVE-2023-50887
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 Syed Balkhi User Feedback userfeedback-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects User Feedback: from n/a through <= 1.0.10.
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 User Feedback WordPress plugin (userfeedback-lite) versions through 1.0.10 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated users to access functionality that should require elevated privileges.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify User Feedback plugin installationCheck if the userfeedback-lite plugin directory exists in your WordPress installation at wp-content/plugins/. List the plugins directory contents.Affected if The userfeedback-lite or user-feedback plugin directory is present in wp-content/plugins/
-
Determine installed plugin versionOpen the main plugin file (typically userfeedback-lite.php or user-feedback.php) in the plugin directory and locate the version header comment, or check the readme.txt file for the Version field.Affected if The reported version is 1.0.10 or lower (any version through 1.0.10)
-
Confirm the vulnerable authorization flaw existsInspect the plugin source code for AJAX endpoints or action handlers that process user submissions. Look for functions that handle feedback submissions without checking user capabilities or nonce validation. Compare your code to the vulnerable version if you have access to older releases.Affected if The plugin processes feedback or survey submissions without requiring authentication or proper capability checks, allowing public access to admin-level functions
-
Test external accessibility of feedback endpointsIf your site is publicly accessible, attempt to access common plugin entry points (such as /wp-admin/admin-ajax.php?action=userfeedback_*) or review server access logs for unauthenticated requests to plugin-related endpoints.Affected if Plugin endpoints are reachable without authentication and respond to requests from non-logged-in users
You are affected if the User Feedback plugin is installed with version 1.0.10 or lower and the vulnerable authorization-less endpoints are accessible to unauthenticated users.
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 User Feedback plugin to the latest available version to obtain patched code, or implement WAF rules/access controls to block unauthorized access to the affected endpoints.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50887 — 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-50887 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