CVE-2018-19549
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.1.6 has SQL Injection via a tagids Delete action to Dynamiccontenttags.php.
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 confidenceSQL Injection vulnerability in Interspire Email Marketer through version 6.1.6. The vulnerability exists in the Dynamiccontenttags.php file, specifically in the tagids parameter during a Delete action. Attackers can inject malicious SQL statements through this parameter to manipulate database queries, potentially exposing sensitive data, modifying or deleting database contents, or escalating privileges.
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.1.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Interspire Email Marketer installationSearch for files named 'index.php', 'admin.php', or 'login.php' with Interspire branding. Check for directory structures containing '/admin/' or '/members/' paths typical of Interspire installations.Affected if Interspire Email Marketer is installed on the server.
-
Identify installed versionCheck for a version file or footer in admin interface. Common locations: /admin/version.php, /version.txt, or examine headers in the login/admin pages for version strings.Affected if The installed version is 6.1.6 or lower.
-
Locate vulnerable fileSearch for the file 'Dynamiccontenttags.php' within the web root, typically under /admin/ or /components/ directories.Affected if Dynamiccontenttags.php exists in the application directory.
-
Verify Delete action is accessibleCheck if the file contains a Delete action handler. Search the source code for 'Delete' or 'delete' operations that process the tagids parameter.Affected if The Delete action exists and processes the tagids parameter.
-
Inspect parameter handlingExamine the Dynamiccontenttags.php code around the tagids parameter to see if it's used in SQL queries without proper sanitization or parameterized queries.Affected if The tagids parameter is directly interpolated into SQL queries without prepared statements.
A user is affected if they have Interspire Email Marketer version 6.1.6 or lower with the Dynamiccontenttags.php file accessible and the tagids 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 dataUpgrade to a patched version of Interspire Email Marketer if available. Alternatively, implement proper input validation and use parameterized queries (prepared statements) for the tagids parameter in the Delete action on Dynamiccontenttags.php. Apply a Web Application Firewall as a temporary compensating control.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19549 — 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-2018-19549 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