CVE-2022-44790
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 · uneditedInterspire Email Marketer through 6.5.1 allows SQL Injection via the surveys module. An unauthenticated attacker could successfully perform an attack to extract potentially sensitive information from the database if the survey id exists.
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 confidenceInterspire Email Marketer through version 6.5.1 contains an unauthenticated SQL injection vulnerability in the surveys module. Attackers can exploit this by manipulating survey ID parameters to inject malicious SQL queries, potentially extracting sensitive data from the database.
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.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Interspire Email Marketer versionLocate the version file or check the admin dashboard footer for the version number. Common locations include a VERSION file in the root directory, the admin header file, or the configuration file.Affected if The installed version is 6.5.1 or any earlier version.
-
Verify the surveys module is presentCheck if the surveys module directory exists in the web root, typically found under /modules/surveys/ or within the main application modules folder.Affected if The surveys module is installed and accessible on the web server.
-
Examine surveys module for vulnerable survey ID parameter handlingInspect the surveys module PHP files (particularly the survey display or submission handlers) to identify if the survey ID parameter is used directly in SQL queries without proper escaping or parameterized queries.Affected if The survey ID parameter is concatenated directly into SQL queries without input sanitization or prepared statements.
-
Check web server access logs for suspicious survey requestsReview web server access logs (Apache, Nginx, or IIS) for requests to the surveys module containing SQL injection patterns in the survey ID parameter, such as UNION SELECT, SLEEP(), or other SQL keywords.Affected if Log analysis reveals unauthenticated requests with SQL injection payloads targeting the survey ID parameter.
A user is affected if running Interspire Email Marketer version 6.5.1 or earlier with the surveys module accessible and the survey ID parameter handled without parameterized queries.
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 dataApply vendor patch or update to a version beyond 6.5.1. If no patch is available, implement input validation and parameterized queries in the surveys module code to neutralize SQL injection vectors.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44790 — 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-2022-44790 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