Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2018-16659: SQL Injection in Rausoft ID.prove 2.95 Login Page

Published Sep 28, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS2.7%87th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Rausoft
IdentifiersCVE-2018-16659CWE-89 · Improper Neutralization of Special…

Rausoft ID.prove 2.95 is vulnerable to SQL injection in the login page, specifically via the Username POST parameter. The vulnerability allows attackers to inject arbitrary SQL, including stacked queries, into Microsoft SQL Server. This can be exploited to execute commands such as master..xp_cmdshell, potentially leading to privilege escalation and remote code execution on the underlying system.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to execute arbitrary SQL commands, potentially leading to full compromise of the database and underlying operating system via xp_cmdshell. This can result in data exfiltration, privilege escalation, and remote code execution.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, disable xp_cmdshell on the SQL Server, restrict database user privileges, and implement web application firewalls to detect and block SQL injection attempts. Monitor logs for suspicious activity related to login attempts and SQL errors.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of Rausoft ID.prove, if available. Ensure all user input is properly sanitized and parameterized queries are used to prevent SQL injection. Disable dangerous SQL Server features such as xp_cmdshell if not required.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
RausoftId.Proveapplication
FAQ

Frequently asked questions

Is CVE-2018-16659 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2018-16659 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2018-16659?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2018-16659.
Is there a patch for CVE-2018-16659?
Upgrade to a fixed version of Rausoft ID.prove, if available. Ensure all user input is properly sanitized and parameterized queries are used to prevent SQL injection.
What products are affected by CVE-2018-16659?
Rausoft Id.Prove.
How severe is CVE-2018-16659?
CVE-2018-16659 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.7% (87th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.