# CVE-2024-39031: Silverpeas Core Cross-site Scripting vulnerability > Attackers can inject XSS payloads into calendar events to execute scripts in victims' browsers, potentially leading to account takeover or data theft. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 9 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-vfwh-gvf6-mff8 ## What is CVE-2024-39031? CVE-2024-39031 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description In Silverpeas Core <= 6.3.5, in Mes Agendas, a user can create new events and add them to their calendar. Additionally, users can invite others from the same domain, including administrators, to these events. A standard user can inject an XSS payload into the "Titre" and "Description" fields when creating an event and then add the administrator or any user to the event. When the invited user (victim) views their own profile, the payload will be executed on their side, even if they do not click on the event. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-39031? 4 open source packages ship an affected version, including org.silverpeas.core:silverpeas-core-rs and org.silverpeas.core:silverpeas-core-web. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.silverpeas.core:silverpeas-core-rs` | Maven | All versions to 6.3.5 | None | | `org.silverpeas.core:silverpeas-core-rs` | Maven | All versions to 6.3.5 | None | | `org.silverpeas.core:silverpeas-core-web` | Maven | All versions to 6.3.5 | None | | `org.silverpeas.core:silverpeas-core-web` | Maven | All versions to 6.3.5 | None | Products: Silverpeas Silverpeas. ## How do I fix CVE-2024-39031? No fix has been published for CVE-2024-39031 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-39031 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39031 exists. Public exploit code: - Stored Cross-Side Scripting (XSS) leads to privilege escalation in SilverPeas social-networking portal (github_poc): https://github.com/toneemarqus/CVE-2024-39031 ## Other vulnerabilities in n/a - [CVE-2018-19586](https://insights.sbomify.com/CVE-2018-19586/): Path traversal in n/a (critical 9.9) - [CVE-2024-42850](https://insights.sbomify.com/CVE-2024-42850/): Silverpeas vulnerable to password complexity rule bypass (critical 9.8) - [CVE-2024-36042](https://insights.sbomify.com/CVE-2024-36042/): Silverpeas authentication bypass (critical 9.8) - [CVE-2023-47322](https://insights.sbomify.com/CVE-2023-47322/): Cross Site Request Forgery in Silverpeas (high 8.8) - [CVE-2023-47326](https://insights.sbomify.com/CVE-2023-47326/): Cross Site Request Forgery in Silverpeas (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-39031 and fix it if it is affected. What it is: CVE-2024-39031 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39031 exists. Affected packages and fixed versions: - org.silverpeas.core:silverpeas-core-rs (Maven): affected all versions up to 6.3.5; no fix listed - org.silverpeas.core:silverpeas-core-rs (Maven): affected all versions up to 6.3.5; no fix listed - org.silverpeas.core:silverpeas-core-web (Maven): affected all versions up to 6.3.5; no fix listed - org.silverpeas.core:silverpeas-core-web (Maven): affected all versions up to 6.3.5; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-39031/ (Markdown: https://insights.sbomify.com/CVE-2024-39031/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39031 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39031 - OSV: https://osv.dev/vulnerability/CVE-2024-39031 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39031/ Summaries are generated and may contain mistakes; the official description above is the record.