dbcve.org
UserfeedbackWordPress extension · Monsterinsights

CVE-2024-5902

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-12
Fix available
A fix is available. Upgrade to 1.0.16 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The User Feedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the name parameter in all versions up to, and including, 1.0.15 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in feedback form responses that will execute whenever a high-privileged user tries to view them.

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 · high confidence

The User Feedback WordPress plugin up to version 1.0.15 fails to sanitize the 'name' parameter during feedback submission and does not escape the output when displaying feedback responses. This allows unauthenticated attackers to submit malicious JavaScript code that gets stored in the database and executes when administrators view the feedback form responses.

MitigationUpdate the User Feedback plugin to version 1.0.16 or later. If immediate update is not possible, consider disabling the feedback form or implementing a Web Application Firewall (WAF) rule to block XSS payloads in the name parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UserfeedbackWordPress extension
Affected:< 1.0.16

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Confirm User Feedback plugin is installed
    Navigate to WordPress admin dashboard > Plugins and check if 'Monsterinsights Userfeedback' or 'User Feedback' plugin appears in the installed plugins list
    Affected if Plugin is installed and active
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find User Feedback, and note the version number displayed under the plugin name
    Affected if Version is 1.0.15 or lower (versions before 1.0.16)
  3. Inspect feedback submissions for suspicious content
    Access the feedback responses area in WordPress admin (typically under User Feedback menu), examine submitted entries, and look for script tags, javascript: URIs, or HTML attributes in the name/submitter field
    Affected if Feedback entries contain unescaped HTML, script tags, or JavaScript code in name fields
  4. Review raw database for stored XSS payloads
    Access phpMyAdmin or use WP-CLI to query the plugin's feedback database table (often named like wp_userfeedback_submissions), search for patterns like <script, javascript:, onerror=, onload= in the name field
    Affected if Database contains unsanitized user input with XSS payloads in name fields

Environment is affected if the User Feedback plugin version is 1.0.15 or earlier, especially if feedback submissions exist with unescaped HTML or script content in name fields.

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
Upgrade available Upgrade to 1.0.16 or later
Fixed in 1.0.16
Interim mitigation

Update the User Feedback plugin to version 1.0.16 or later. If immediate update is not possible, consider disabling the feedback form or implementing a Web Application Firewall (WAF) rule to block XSS payloads in the name parameter.

Recommended fix High confidence

1.0.16

  1. 1. Backup your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins.
  3. 3. Locate the User Feedback plugin in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to update to version 1.0.16.
  5. 5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the version 1.0.16 of the User Feedback plugin.
  6. 6. After updating, verify the plugin status shows version 1.0.16.

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

Fix this in Userfeedback Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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