dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 May 2023.
Novi SurveyApplication · 3rdmill

CVE-2023-29492

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 8.9.43676 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click

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
Novi Survey before 8.9.43676 allows remote attackers to execute arbitrary code on the server in the context of the service account. This does not provide access to stored survey or response data.

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

Novi Survey before version 8.9.43676 contains a pre-authentication remote code execution vulnerability that allows unauthenticated remote attackers to execute arbitrary commands on the server with the privileges of the service account running the application.

MitigationUpgrade Novi Survey to version 8.9.43676 or later to remediate the vulnerability. If immediate patching is not possible, restrict network access to the application to reduce exposure.

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
Novi SurveyApplication
Affected:< 8.9.43676

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Novi Survey is installed
    Check your system for Novi Survey applications or services. Look for processes named 'Novi Survey' or check installed programs list.
    Affected if Novi Survey is found on the system
  2. Determine the installed Novi Survey version
    Access the Novi Survey admin interface or check the application binaries for version information. The version is typically displayed in the About section of the application or in the installation directory.
    Affected if The installed version is before 8.9.43676 or cannot be determined
  3. Check application accessibility
    Verify whether the Novi Survey web interface is exposed to network access. Check firewall rules and application binding configuration.
    Affected if The application is accessible from untrusted networks without authentication barriers
  4. Confirm the unauthenticated endpoint is reachable
    Identify if public-facing endpoints exist that handle survey submissions or user input without requiring authentication.
    Affected if Unauthenticated endpoints are exposed and reachable from external networks

If Novi Survey is installed and the version is lower than 8.9.43676, the environment is affected by this unauthenticated RCE vulnerability.

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

Upgrade Novi Survey to version 8.9.43676 or later to remediate the vulnerability. If immediate patching is not possible, restrict network access to the application to reduce exposure.

Recommended fix High confidence

8.9.43676 or later

  1. 1. Backup the current Novi Survey installation and database before proceeding with any upgrade.
  2. 2. Download the latest version of Novi Survey (version 8.9.43676 or later) from the official vendor website (novisurvey.net) or your licensed download portal.
  3. 3. Review the vendor's upgrade documentation and release notes for version 8.9.43676.
  4. 4. Execute the upgrade installer on the server following the vendor's standard upgrade procedure.
  5. 5. Verify the upgrade was successful by checking the application version in the admin interface.
  6. 6. Test critical survey functionality to ensure the upgrade did not break existing surveys or integrations.
  7. 7. After upgrading, confirm the vulnerability is remediated by verifying the server no longer accepts unauthenticated code injection requests.

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

Fix this in Novi Survey Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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