CVE-2019-7941
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 · uneditedAdobe Campaign Classic version 18.10.5-8984 and earlier versions have an Information Exposure Through an Error Message vulnerability. Successful exploitation could lead to Information Disclosure in the context of the current user.
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 · moderate confidenceAdobe Campaign Classic versions 18.10.5-8984 and earlier contain an information exposure vulnerability where error messages leak sensitive information to users. The flaw allows authenticated users to potentially access data outside their authorized scope through verbose or unsanitized error responses.
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<= 18.10.5.8984CVSS 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.0/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 Adobe Campaign Classic versionLocate the Adobe Campaign installation directory and check the version file or execute: nlserver -version (or check the about/info page in the client console). Compare the version number to the affected range: versions <= 18.10.5.8984 are vulnerable.Affected if Installed version is 18.10.5-8984 or earlier (or any build number below 8984).
-
Review web server configuration for error handlingExamine the Apache/IIS configuration files in the Adobe Campaign web directory (conf/serverConf.xml or similar). Look for 'debug' or 'verbose' settings in the error handling sections.Affected if Error handling is configured to return stack traces, database details, or full system messages to users.
-
Test error response contentTrigger an intentional error condition (such as accessing a non-existent element, submitting invalid data, or causing a server-side failure) while logged in as a standard user. Capture the full HTTP response.Affected if The error response reveals internal file paths, database connection strings, stack traces, user identifiers beyond scope, or other sensitive system information.
-
Inspect XML configuration for displayErrors settingCheck the conf/config.xml or conf/serverConf.xml file for the 'displayErrors' parameter. This setting controls whether detailed errors are shown to clients.Affected if displayErrors is set to 'true' or a non-zero value, allowing verbose error output to reach users.
A user is affected if their Adobe Campaign Classic installation is version 18.10.5-8984 or earlier AND error responses expose sensitive information (stack traces, paths, database details) to authenticated users.
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 proper error handling that returns generic error messages to users while logging detailed information server-side; review all error paths to ensure sensitive data (stack traces, database details, file paths, user data) is not exposed in responses.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7941 — 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-7941 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