dbcve.org
NexposeApplication · Rapid7

CVE-2022-0758

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-17
Fix available
A fix is available. Upgrade to 6.6.130 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
Rapid7 Nexpose versions 6.6.129 and earlier suffer from a reflected cross site scripting vulnerability, within the shared scan configuration component of the tool. With this vulnerability an attacker could pass literal values as the test credentials, providing the opportunity for a potential XSS attack. This issue is fixed in Rapid7 Nexpose version 6.6.130.

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

Rapid7 Nexpose versions 6.6.129 and earlier contain a reflected XSS vulnerability in the shared scan configuration component. The vulnerability allows attackers to inject malicious script via test credential fields that are not properly sanitized before being rendered back to users.

MitigationUpgrade to Rapid7 Nexpose version 6.6.130 or later to obtain the patch for this vulnerability.

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
NexposeApplication
Affected:< 6.6.130

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. Determine the installed Nexpose version
    Log into the Nexpose console and navigate to Administration > System > Troubleshooting, or use the Nexpose API endpoint /api/3.1/system/info to retrieve the current version number
    Affected if The installed version is 6.6.129 or earlier (any version below 6.6.130)
  2. Locate shared scan configurations
    In the Nexpose console, navigate to the Shared Scan Configuration section under the scan templates or assets area to identify any configured shared scan configurations
    Affected if One or more shared scan configurations exist in the Nexpose instance
  3. Review test credential fields in shared scan configurations
    Open any existing shared scan configuration and access the credential settings. Use the test credential functionality to verify if the response displays unsanitized input
    Affected if Test credentials are executed and the results are reflected back in the interface without proper encoding or sanitization

You are affected if your Rapid7 Nexpose installation is version 6.6.129 or earlier and you have used the test credential feature within shared scan configurations.

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

Upgrade to Rapid7 Nexpose version 6.6.130 or later to obtain the patch for this vulnerability.

Recommended fix High confidence

Rapid7 Nexpose version 6.6.130

  1. 1. Check current Nexpose version by logging into the management console and navigating to the Administration > System > Updates section
  2. 2. Back up the Nexpose configuration and database according to standard backup procedures before upgrading
  3. 3. Download Rapid7 Nexpose version 6.6.130 from the official Rapid7 download portal or support website
  4. 4. Stop the Nexpose service to ensure a clean upgrade process
  5. 5. Run the installer for version 6.6.130, following the on-screen prompts
  6. 6. After installation completes, restart the Nexpose service
  7. 7. Verify the upgrade was successful by checking the version in the Administration console
  8. 8. Test the shared scan configuration component to confirm the XSS vulnerability is no longer present
Caveat As this is a patch release (6.6.129 to 6.6.130), breaking changes are unlikely. However, standard practice recommends testing in a non-production environment first

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

Fix this in Nexpose Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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