CVE-2024-2211
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 · uneditedCross-Site Scripting stored vulnerability in Gophish affecting version 0.12.1. This vulnerability could allow an attacker to store a malicious JavaScript payload in the campaign menu and trigger the payload when the campaign is removed from the menu.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Gophish 0.12.1 allows attackers to inject malicious JavaScript payloads into the campaign menu. The payload persists in the application and executes when the campaign is subsequently removed from the menu, potentially allowing session hijacking or actions as the victim.
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= 0.12.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Gophish installation and versionCheck the installed Gophish version by reviewing the binary or checking the application startup logs. Common locations: look for the gophish binary or check /opt/gophish, /home/<user>/gophish, or the directory where Gophish was installed. Run 'gophish --version' if accessible or check the binary file info.Affected if The installed version is exactly 0.12.1 (note: version equality means only this specific version is affected)
-
Confirm campaign feature is in useCheck if campaigns have been created in the Gophish application. Access the Gophish web interface and navigate to the Campaigns section, or query the underlying database (typically SQLite or MySQL) for records in the campaigns table.Affected if Campaigns exist in the system; the vulnerability only triggers when a crafted campaign is removed from the menu
-
Inspect campaign entries for suspicious scriptsExamine campaign names and associated metadata for HTML/script content. In the database, review the campaigns table for entries containing <script>, javascript:, onload, onerror, or other XSS vectors in fields like campaign_name or related text fields. Alternatively, view campaigns through the web interface and inspect page source for injected payloads.Affected if Any campaign entry contains JavaScript code or HTML tags (such as <script>, <img onerror=>, <svg onload=>) in its name or campaign-related fields
You are affected if you are running Gophish version 0.12.1 AND have created campaigns that may contain maliciously crafted payloads in campaign name or related fields, which will execute when that campaign is removed from the menu.
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 a patched version of Gophish if available; otherwise, implement server-side input validation and output encoding for all campaign-related fields to prevent XSS execution.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2211 — 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-2211 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