CVE-2024-23736
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 Request Forgery (CSRF) vulnerability in savignano S/Notify before 4.0.2 for Confluence allows attackers to manipulate a user's S/MIME certificate of PGP key via malicious link or email.
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 confidenceCross Site Request Forgery (CSRF) vulnerability in savignano S/Notify plugin for Confluence versions before 4.0.2 allows authenticated attackers to manipulate a user's S/MIME certificate or PGP key by tricking a logged-in user into clicking a malicious link or viewing a crafted email, exploiting the lack of anti-CSRF tokens on sensitive certificate/key management functions.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Confirm S/Notify plugin is installedIn Confluence admin console, navigate to Manage Apps or Plugins section and verify that the savignano S/Notify plugin appears in the list of installed pluginsAffected if The plugin is not listed in installed apps
-
Identify installed S/Notify versionIn the Manage Apps section, locate the savignano S/Notify entry and note the version number displayed in the plugin detailsAffected if Version is blank or cannot be determined from the plugin metadata
-
Compare version against vulnerable rangeCompare the installed version to 4.0.2 - any version lower than 4.0.2 (including 4.0.1, 4.0.0, 3.x.x, etc.) is affectedAffected if Installed version is less than 4.0.2 (e.g., 4.0.1, 3.9.5, etc.)
-
Verify certificate/key features are accessibleCheck if S/MIME certificate or PGP key management features are available in the plugin settings or user profile sections accessible to authenticated usersAffected if S/MIME or PGP key management functions are present and accessible to users
You are affected if the S/Notify plugin is installed with a version lower than 4.0.2 and users can access S/MIME or PGP key management functions.
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.
dbcve · scopedUpgrade savignano S/Notify for Confluence to version 4.0.2 or later to obtain the CSRF fix. Alternatively, implement anti-CSRF tokens on all state-changing endpoints and validate the Origin/Referer headers.
4.0.2
- Upgrade savignano S/Notify for Confluence to version 4.0.2 or later to resolve the CSRF vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.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,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23736 — 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-23736 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