diff --git a/advisories/github-reviewed/2024/01/GHSA-53ph-2r2x-vqw8/GHSA-53ph-2r2x-vqw8.json b/advisories/github-reviewed/2024/01/GHSA-53ph-2r2x-vqw8/GHSA-53ph-2r2x-vqw8.json
index 27a90abf23e..22e5cbae0d5 100644
--- a/advisories/github-reviewed/2024/01/GHSA-53ph-2r2x-vqw8/GHSA-53ph-2r2x-vqw8.json
+++ b/advisories/github-reviewed/2024/01/GHSA-53ph-2r2x-vqw8/GHSA-53ph-2r2x-vqw8.json
@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-53ph-2r2x-vqw8",
-  "modified": "2024-01-26T01:57:04Z",
+  "modified": "2024-01-31T20:22:29Z",
   "published": "2024-01-24T18:31:02Z",
   "aliases": [
     "CVE-2024-23898"
@@ -9,7 +9,10 @@
   "summary": "Cross-site WebSocket hijacking vulnerability in the Jenkins CLI",
   "details": "\n\nJenkins has a built-in command line interface (CLI) to access Jenkins from a script or shell environment. Since Jenkins 2.217 and LTS 2.222.1, one of the ways to communicate with the CLI is through a WebSocket endpoint. This endpoint relies on the default Jenkins web request authentication functionality, like HTTP Basic authentication with API tokens, or session cookies. This endpoint is enabled when running on a version of Jetty for which Jenkins supports WebSockets. This is the case when using the provided native installers, packages, or the Docker containers, as well as when running Jenkins with the command java -jar jenkins.war.\n\nJenkins 2.217 through 2.441 (both inclusive), LTS 2.222.1 through 2.426.2 (both inclusive) does not perform origin validation of requests made through the CLI WebSocket endpoint, resulting in a cross-site WebSocket hijacking (CSWSH) vulnerability.\n",
   "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
+    }
   ],
   "affected": [
     {
@@ -82,7 +85,7 @@
   ],
   "database_specific": {
     "cwe_ids": [
-
+      "CWE-346"
     ],
     "severity": "HIGH",
     "github_reviewed": true,
diff --git a/advisories/github-reviewed/2024/01/GHSA-cjgm-9vc9-56mx/GHSA-cjgm-9vc9-56mx.json b/advisories/github-reviewed/2024/01/GHSA-cjgm-9vc9-56mx/GHSA-cjgm-9vc9-56mx.json
index 4339a1f2861..6db8af5445f 100644
--- a/advisories/github-reviewed/2024/01/GHSA-cjgm-9vc9-56mx/GHSA-cjgm-9vc9-56mx.json
+++ b/advisories/github-reviewed/2024/01/GHSA-cjgm-9vc9-56mx/GHSA-cjgm-9vc9-56mx.json
@@ -1,15 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-cjgm-9vc9-56mx",
-  "modified": "2024-01-24T21:48:53Z",
+  "modified": "2024-01-31T20:23:24Z",
   "published": "2024-01-24T18:31:02Z",
   "aliases": [
     "CVE-2024-23900"
   ],
   "summary": "Path traversal vulnerability in Jenkins Matrix Project Plugin",
-  "details": "Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects, allowing attackers with Item/Configure permission to create or replace any config.xml files on the Jenkins controller file system with content not controllable by the attackers.",
+  "details": "Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects submitted through the `config.xml` REST API endpoint.\n\nThis allows attackers with Item/Configure permission to create or replace any `config.xml` file on the Jenkins controller file system with content not controllable by the attackers.\n\nMatrix Project Plugin 822.824.v14451b_c0fd42 sanitizes user-defined axis names of Multi-configuration project.",
   "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L"
+    }
   ],
   "affected": [
     {