CampaignApplication · Adobe

CVE-2019-7843

HIGH · 7.5 CVSS v3.0 Published 2019-07-18
Fix available
A fix is available. Upgrade to after 18.10.5.8984 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Adobe Campaign Classic version 18.10.5-8984 and earlier versions have an Insufficient input validation 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 · high confidence

This is an input validation vulnerability in Adobe Campaign Classic where insufficient validation of user-supplied input allows an authenticated attacker to access sensitive information beyond what their current user context should permit. The flaw enables unauthorized disclosure of data that should be restricted.

MitigationApply the vendor-provided patch or upgrade to a patched version of Adobe Campaign Classic beyond 18.10.5-8984. Additionally, implement robust input validation and sanitization on all user-facing fields as a defense-in-depth measure.

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
CampaignApplication
Affected:<= 18.10.5.8984

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe Campaign Classic version
    Access the Adobe Campaign Classic client or web interface and navigate to the About or Version information section, typically found in Help > About or the dashboard. Alternatively, check the installation directory for a version file or examine the server logs for startup version information.
    Affected if The installed version is 18.10.5.8984 or earlier (any version <= 18.10.5.8984)
  2. Confirm Campaign installation type
    Verify that the installation is Adobe Campaign Classic (not Adobe Campaign Standard). This vulnerability affects only the Classic variant. Check the product name in the About section or in the installation documentation.
    Affected if The product is Adobe Campaign Classic and the version falls within the affected range
  3. Review user access controls
    Examine the user roles and permissions configured in Adobe Campaign Classic. Navigate to Administration > Access Management > Named Rights or similar permission configuration panels to review what data access each user role has been granted.
    Affected if Users with limited roles have been granted access to sensitive data or schemas outside their intended scope, indicating the vulnerability may be present
  4. Check audit logs for unauthorized data access
    Locate and review Adobe Campaign Classic audit logs, typically found in the installation logs directory or within the platform's monitoring interface. Look for queries or data access operations from authenticated users accessing data outside their normal permissions.
    Affected if Logs show authenticated users accessing data or schemas beyond what their assigned roles should permit

A user is affected if Adobe Campaign Classic version 18.10.5.8984 or earlier is installed and the application processes user-supplied input that could be manipulated to bypass access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 18.10.5.8984
Interim mitigation

Apply the vendor-provided patch or upgrade to a patched version of Adobe Campaign Classic beyond 18.10.5-8984. Additionally, implement robust input validation and sanitization on all user-facing fields as a defense-in-depth measure.

Fix this in Campaign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7843 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7843 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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