CVE-2019-5630
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability was found in Rapid7 Nexpose InsightVM Security Console versions 6.5.0 through 6.5.68. This issue allows attackers to exploit CSRF vulnerabilities on API endpoints using Flash to circumvent a cross-domain pre-flight OPTIONS request.
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 confidenceA CSRF vulnerability in Rapid7 Nexpose InsightVM Security Console (versions 6.5.0-6.5.68) allows attackers to execute unauthorized actions on API endpoints by leveraging Flash to bypass cross-domain pre-flight OPTIONS request protections. Attackers can trick authenticated users into performing unintended API operations.
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>= 6.5.0, <= 6.5.68CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Rapid7 Nexpose InsightVM is installedLocate the InsightVM installation directory or check running services for 'nexpose' or 'insightvm' processes. On Windows, look in C:\Program Files\Rapid7\ or C:\Program Files (x86)\Rapid7\. On Linux, check /opt/rapid7/ or /etc/init.d/ for nexpose services.Affected if The product is not present on the system.
-
Identify the installed InsightVM versionCheck the version file in the installation directory, or use the product's built-in version command if available. Common locations include a version.txt file or the product's About/Support page in the web console.Affected if The installed version is greater than or equal to 6.5.0 and less than or equal to 6.5.68.
-
Verify the API console is accessibleAttempt to access the InsightVM Security Console API endpoint (typically port 3780 or 443) via HTTPS. Confirm the web interface or API is responding to requests.Affected if The API or web console is not accessible or not enabled.
-
Check if Flash plugin support exists in the environmentReview browser or client configurations for legacy Flash support. While this is a server-side vulnerability, the attack vector involves Flash making requests from a client browser.Affected if Clients have Flash plugin access to the browser used for accessing InsightVM.
You are affected if Rapid7 Nexpose InsightVM version 6.5.0 through 6.5.68 is installed and the API console is accessible with potential Flash-based request capabilities.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of InsightVM and ensure proper CSRF token validation is enforced on all API endpoints to prevent Flash-based preflight bypasses.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5630 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5630 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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