dbcve.org
Survey MakerWordPress extension · Ays Pro

CVE-2023-34423

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 3.6.4 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
Survey Maker prior to 3.6.4 contains a stored cross-site scripting vulnerability. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who is logging in to the website using the product with the administrative privilege.

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 confidence

This is a stored cross-site scripting (XSS) vulnerability in the Survey Maker WordPress plugin before version 3.6.4. The flaw allows an attacker to inject malicious JavaScript code into survey fields, which is then stored in the database and executed when an administrator logs in and views the affected survey data.

MitigationUpgrade to Survey Maker version 3.6.4 or later, which contains the security patch for this vulnerability. As a temporary measure, implement output encoding and input validation on survey submission endpoints.

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
Survey MakerWordPress extension
Affected:< 3.6.4

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. Verify Survey Maker plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Survey Maker' or 'AYS Pro Survey Maker' in the list. Note the installed version displayed below the plugin name.
    Affected if Plugin is present and active in the WordPress installation
  2. Compare installed version to vulnerable range
    Check the plugin version number against the affected range: versions prior to 3.6.4 are vulnerable. The version is typically displayed on the Plugins page or in the plugin's readme.txt file at /wp-content/plugins/ays-survey-maker/readme.txt
    Affected if Installed version is lower than 3.6.4 (for example, 3.6.3, 3.6.0, etc.)
  3. Inspect survey forms for user input fields
    Navigate to Survey Maker in the WordPress admin panel and review all created surveys. Identify surveys that contain text input fields, textarea fields, or multiple-choice options that accept freeform user input.
    Affected if Any survey contains input fields that accept freeform text from users
  4. Examine stored survey submissions for malicious content
    Access survey results or submissions through Survey Maker > Results. Look for survey entries containing script tags, javascript: URLs, onload/onerror attributes, or other HTML/JavaScript in text fields that were not intentionally added by administrators.
    Affected if Any survey submission database records contain unsanitized HTML or JavaScript code patterns

The environment is affected if the Survey Maker plugin is installed with a version lower than 3.6.4 and contains surveys with user input fields that may have been exploited to store malicious scripts.

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 3.6.4 or later
Fixed in 3.6.4
Interim mitigation

Upgrade to Survey Maker version 3.6.4 or later, which contains the security patch for this vulnerability. As a temporary measure, implement output encoding and input validation on survey submission endpoints.

Recommended fix High confidence

3.6.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Survey Maker plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.6.4
  5. 5. Alternatively, download version 3.6.4 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After upgrading, verify the plugin version shows 3.6.4 or higher

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

Fix this in Survey Maker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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