CVE-2023-50887: WordPress User Feedback plugin <= 1.0.10 - Broken Access Control vulnerability
Missing 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.
Security readout for executives and security teams
Plain-English summary
This is a broken access control issue in the WordPress User Feedback plugin. A remote unauthenticated actor may be able to perform an unauthorized action with limited integrity impact. The public bundle does not show data theft, service outage, or confirmed exploitation.
Executive priority
Treat as a moderate-priority WordPress exposure item. Prioritize internet-facing business sites, customer-facing marketing sites, and sites where plugin-controlled content or feedback data could affect trust or operations.
Technical view
CVE-2023-50887 is CWE-862 missing authorization in Syed Balkhi User Feedback userfeedback-lite through version 1.0.10. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only.
Likely exposure
Exposure is likely limited to WordPress sites with the User Feedback plugin userfeedback-lite installed at version 1.0.10 or earlier. The source bundle provides no CPEs and no details on specific vulnerable endpoints.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not claim active exploitation. The score indicates unauthenticated network reachability, but the documented impact is limited to integrity, not confidentiality or availability.
Researcher notes
Evidence is sparse. The bundle identifies missing authorization and low integrity impact, but does not provide endpoint detail, patch version, exploit proof, or observed attacks. Avoid assuming broader compromise without vendor evidence.
Mitigation direction
Inventory WordPress sites for User Feedback userfeedback-lite versions 1.0.10 or earlier.
Check vendor, WordPress plugin, or Patchstack guidance for a fixed version.
Update the plugin if a vendor-supported fixed version is available.
Disable or remove the plugin where it is not business-critical.
Use access controls or WAF rules to reduce unauthenticated exposure where practical.
Validation and detection
Confirm whether each WordPress instance has userfeedback-lite installed.
Record installed plugin versions and flag 1.0.10 or earlier.
Review administrative and plugin-related logs for unexpected changes.
Verify remediation by confirming the plugin is updated, disabled, or removed.
Track findings where fixed-version evidence is unavailable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.