dbcve.org
S NotifyApplication · Savignano

CVE-2024-23735

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross Site Scripting (XSS) vulnerability in in the S/MIME certificate upload functionality of the User Profile pages in savignano S/Notify before 4.0.0 for Confluence allows attackers to manipulate user data via specially crafted certificate.

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 confidence

A stored XSS vulnerability exists in the S/MIME certificate upload functionality within User Profile pages of savignano S/Notify for Confluence. The application fails to properly sanitize or validate uploaded certificate files, allowing attackers to embed malicious script that executes when users view the uploaded certificate in their profile.

MitigationUpgrade to S/Notify version 4.0.0 or later which contains the fix. If immediate upgrade is not possible, restrict S/MIME certificate upload permissions and monitor for suspicious certificate uploads.

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
S NotifyApplication
Affected:< 4.0.0

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

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

  1. Confirm S/Notify plugin is installed
    Navigate to Confluence Administration > Apps > Manage apps (or Universal Plugin Manager) and search for 'S/Notify' or 'Savignano' in the installed applications list
    Affected if The S/Notify application does not appear in the installed apps list - you are not using the affected product
  2. Identify installed S/Notify version
    In the Manage apps section, locate the S/Notify entry and note the version number displayed. Compare this version to the affected range: versions prior to 4.0.0
    Affected if The installed version is less than 4.0.0 (for example, 3.x.x or any version number below 4.0.0)
  3. Check if S/MIME certificate upload is accessible
    Navigate to your Confluence user profile settings and look for S/MIME certificate upload or S/Notify certificate configuration options. Check if the certificate upload feature is present and enabled for your profile
    Affected if The S/MIME certificate upload feature is visible and accessible in the user profile settings - the vulnerable code path exists in your environment
  4. Review uploaded certificates in the system
    As an administrator, check S/Notify settings or examine uploaded certificate files stored in the Confluence database or file system for any certificates containing suspicious script content
    Affected if Any certificates contain unexpected JavaScript tags, script elements, or suspicious encoded content that could indicate exploitation

You are affected if S/Notify is installed with a version lower than 4.0.0 and the S/MIME certificate upload feature is accessible to users in your Confluence environment.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade to S/Notify version 4.0.0 or later which contains the fix. If immediate upgrade is not possible, restrict S/MIME certificate upload permissions and monitor for suspicious certificate uploads.

Recommended fix High confidence

4.0.0

  1. Access the Confluence administration console
  2. Navigate to the apps/Add-ons management section
  3. Find S Notify in the list of installed apps
  4. Click on the S Notify app to view details
  5. Look for an update option or check for available updates
  6. Upgrade to version 4.0.0 or later
  7. Verify the upgrade was successful and the app is functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in S Notify 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-2024-23735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-23735 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