dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57361

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

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
Unauthenticated Cross Site Scripting (XSS) in Survey Maker <= 5.2.2.5 versions.

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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the Survey Maker plugin/theme for versions 5.2.2.5 and below. Attackers can inject malicious scripts into survey forms without authentication, potentially stealing session cookies or performing actions on behalf of users.

MitigationUpgrade Survey Maker to version 5.2.2.6 or later. If immediate patching is not possible, implement WAF rules to filter XSS payloads and disable the plugin until upgrade is feasible.

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

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

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

  1. Identify if Survey Maker is installed
    Locate the Survey Maker plugin or theme in your CMS/website's plugin or theme directory. Common locations include /wp-content/plugins/ for WordPress or similar paths in other CMS platforms.
    Affected if Survey Maker plugin or theme is present on the system
  2. Determine the installed version
    Check the version information in the plugin/theme metadata file (such as readme.txt, plugin.php header, or theme style.css). Look for a 'Version:' field.
    Affected if The reported version is 5.2.2.5 or any version lower than 5.2.2.6
  3. Verify unauthenticated survey form access
    Test accessing a public survey form created with Survey Maker without logging in. Submit a test response with simple HTML content to see if it is reflected in the output.
    Affected if Survey forms are publicly accessible and input is not properly sanitized or escaped in the response
  4. Inspect survey form configurations
    Review the survey form settings in the Survey Maker admin panel. Check if there are any custom scripts or unexpected JavaScript entries in form fields, questions, or response messages.
    Affected if Unexpected script tags or JavaScript event handlers appear in survey field configurations

You are affected if Survey Maker is installed with version 5.2.2.5 or below and survey forms are accessible to unauthenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Survey Maker to version 5.2.2.6 or later. If immediate patching is not possible, implement WAF rules to filter XSS payloads and disable the plugin until upgrade is feasible.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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