CVE-2018-19651
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 · uneditedadmin/functions/remote.php in Interspire Email Marketer through 6.1.6 has Server Side Request Forgery (SSRF) via a what=importurl&url= request with an http or https URL. This also allows reading local files with a file: URL.
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 6.1.6 contains an SSRF vulnerability in admin/functions/remote.php where the 'url' parameter accepts arbitrary URLs including file: scheme. An authenticated attacker can force the server to make requests to internal services, access cloud metadata endpoints, or read local filesystem files by supplying file:// URLs.
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.6= 6.1.8CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 Interspire Email Marketer installationLocate the main installation directory (commonly under /, /var/www, or web root). Look for the main index.php file or the 'admin' directory that contains the Interspire Email Marketer application.Affected if The software is Interspire Email Marketer and the admin/functions/remote.php file exists in the installation.
-
Determine the installed versionCheck the version by examining the admin/functions/remote.php file header comments, or look for a version file in the installation root. The affected versions are 6.1.6 and below, and version 6.1.8.Affected if The installed version is 6.1.6 or lower, or exactly 6.1.8.
-
Verify the vulnerable remote.php file is presentConfirm that the file admin/functions/remote.php exists in the installation. This file contains the vulnerable code that processes the 'url' parameter.Affected if The file admin/functions/remote.php exists and contains code that accepts a 'url' parameter for making HTTP/file requests.
-
Confirm administrative access is possibleDetermine if the application's admin panel is accessible. This vulnerability requires an authenticated attacker, so check if weak credentials are in use or if the admin area is exposed.Affected if The admin panel is accessible with valid credentials, or the authentication mechanism can be bypassed.
You are affected if Interspire Email Marketer versions 6.1.6 or below, or version 6.1.8 is installed, the admin/functions/remote.php file exists, and the admin interface is accessible to an attacker who can supply arbitrary URLs to the 'url' parameter.
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 dataImplement strict input validation on the url parameter to whitelist allowed URL schemes (block file:, and restrict http/https to allowed domains/IPs), add network segmentation to prevent the application server from accessing internal resources, and apply principle of least privilege to file system access.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19651 — 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-19651 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