CVE-2024-49285
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Jeroen Berkvens SSV MailChimp ssv-mailchimp allows PHP Local File Inclusion.This issue affects SSV MailChimp: from n/a through <= 3.1.5.
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 confidencePath traversal vulnerability in SSV MailChimp plugin allows attackers to use '../' sequences in user-controlled input to include arbitrary PHP files from the filesystem, potentially executing malicious code or reading sensitive files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Identify if SSV MailChimp plugin is installedCheck your WordPress plugins directory or plugin manifest for 'SSV MailChimp' or 'SSV' related MailChimp integration filesAffected if The SSV MailChimp plugin is present in the installation
-
Determine the installed version of SSV MailChimp pluginReview the plugin header in the main PHP file (commonly in wp-content/plugins/ssv-mailchimp/ or similar path) for the Version field, or check via WordPress plugin admin interfaceAffected if Version is unknown or falls within an unpatched range prior to the fix
-
Verify if file inclusion or template features are enabledInspect plugin settings in WordPress admin under SSV MailChimp configuration pages for options like 'custom templates', 'include files', 'custom email templates', or any feature allowing PHP file inclusionAffected if File inclusion or custom template features are active and accessible to users
-
Check for accessible endpoints that accept file pathsReview plugin source code for functions handling include, require, or similar file operations that process user input, and test if HTTP parameters can inject '../' sequencesAffected if Plugin exposes endpoints that process file paths from user input without strict validation
-
Monitor access logs for path traversal attemptsSearch web server logs (Apache/Nginx) for patterns containing '../' in requests to SSV MailChimp plugin endpoints, such as ?file=../../ or ?template=../../Affected if Suspicious path traversal patterns are found in logs targeting the plugin
Affected if SSV MailChimp plugin is installed, uses a vulnerable version with file inclusion features enabled, and exposes user-controllable input that can be manipulated with '../' sequences.
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 dataUpdate to patched version if available; otherwise implement strict input validation to reject path traversal sequences ('../') and ensure all file inclusion operations stay within allowed directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49285 — 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-2024-49285 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