diff --git a/2018/15xxx/CVE-2018-15728.json b/2018/15xxx/CVE-2018-15728.json
index 02eebd5614a..bfea09456c4 100644
--- a/2018/15xxx/CVE-2018-15728.json
+++ b/2018/15xxx/CVE-2018-15728.json
@@ -34,7 +34,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An issue was discovered in Couchbase Server. Authenticated users can send arbitrary Erlang code to the 'diag/eval' endpoint of the REST API (available by default on TCP/8091 and/or TCP/18091). The executed code in the underlying operating system will run with the privileges of the user running Couchbase server."
+                "value": "Couchbase Server exposed the '/diag/eval' endpoint which by default is available on TCP/8091 and/or TCP/18091. Authenticated users that have 'Full Admin' role assigned could send arbitrary Erlang code to the 'diag/eval' endpoint of the API and the code would subsequently be executed in the underlying operating system with privileges of the user which was used to start Couchbase. Affects Version: 4.0.0, 4.1.2, 4.5.1, 5.0.0, 4.6.5, 5.0.1, 5.1.1, 5.5.0, 5.5.1. Fix Version: 6.0.0, 5.5.2"
             }
         ]
     },
diff --git a/2019/11xxx/CVE-2019-11464.json b/2019/11xxx/CVE-2019-11464.json
index d08a146b5a0..08ba3c973a8 100644
--- a/2019/11xxx/CVE-2019-11464.json
+++ b/2019/11xxx/CVE-2019-11464.json
@@ -34,7 +34,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An issue was discovered in Couchbase Server 5.1.2 and 5.5.0. The http server on port 8092 lacks an X-XSS protection header."
+                "value": "Some enterprises require that REST API endpoints include security-related headers in REST responses. Headers such as X-Frame-Options and X-Content-Type-Options are generally advisable, however some information security professionals additionally look for X-Permitted-Cross-Domain-Policies and X-XSS-Protection, which are more generally applicable to HTML endpoint, to be included too. These headers were not included in Couchbase Server 5.5.0 and 5.1.2 . They are now included in version 6.0.2 in responses from the Couchbase Server Views REST API (port 8092)."
             }
         ]
     },
diff --git a/2019/11xxx/CVE-2019-11467.json b/2019/11xxx/CVE-2019-11467.json
index a8818c0de54..6963b82cfff 100644
--- a/2019/11xxx/CVE-2019-11467.json
+++ b/2019/11xxx/CVE-2019-11467.json
@@ -34,7 +34,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An issue was discovered in Couchbase Server 4.6.3 and 5.5.0. A JSON document to be stored with more than 3000 '\\t' characters can crash the indexing system."
+                "value": "In Couchbase Server 4.6.3 and 5.5.0, secondary indexing encodes the entries to be indexed using collatejson. When index entries contain certain characters like \\t, <, >, it caused buffer overrun as encoded string would be much larger than accounted for, causing indexer service to crash and restart. This has been remedied in versions 5.1.2 and 5.5.2 to ensure buffer always grows as needed for any input."
             }
         ]
     },
diff --git a/2019/11xxx/CVE-2019-11497.json b/2019/11xxx/CVE-2019-11497.json
index ae35e036b57..0aa18f4a602 100644
--- a/2019/11xxx/CVE-2019-11497.json
+++ b/2019/11xxx/CVE-2019-11497.json
@@ -34,7 +34,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An issue was discovered in Couchbase Server 5.0.0. When creating a new remote cluster reference in Couchbase for XDCR, an invalid certificate is accepted. (The correct behavior is to validate the certificate against the remote cluster.)"
+                "value": "In Couchbase Server 5.0.0, when an invalid Remote Cluster Certificate was entered as part of the reference creation, XDCR did not parse and check the certificate signature. It then accepted the invalid certificate and attempted to use it to establish future connections to the remote cluster. This has been fixed in version 5.5.0. XDCR now checks the validity of the certificate thoroughly and prevents a remote cluster reference from being created with an invalid certificate."
             }
         ]
     },
diff --git a/2019/12xxx/CVE-2019-12405.json b/2019/12xxx/CVE-2019-12405.json
index ef8da43adda..8bb7ae7f0da 100644
--- a/2019/12xxx/CVE-2019-12405.json
+++ b/2019/12xxx/CVE-2019-12405.json
@@ -48,6 +48,11 @@
                 "refsource": "MLIST",
                 "name": "[trafficcontrol-users] 20190906 CVE-2019-12405: Apache Traffic Control LDAP-based authentication vulnerability",
                 "url": "https://lists.apache.org/thread.html/e128e9d382f3b0d074e2b597ac58e1d92139394509d81ddbc9e3700e@%3Cusers.trafficcontrol.apache.org%3E"
+            },
+            {
+                "refsource": "CONFIRM",
+                "name": "https://support.f5.com/csp/article/K84141859",
+                "url": "https://support.f5.com/csp/article/K84141859"
             }
         ]
     },
diff --git a/2019/16xxx/CVE-2019-16667.json b/2019/16xxx/CVE-2019-16667.json
new file mode 100644
index 00000000000..109ab0afe6b
--- /dev/null
+++ b/2019/16xxx/CVE-2019-16667.json
@@ -0,0 +1,62 @@
+{
+    "CVE_data_meta": {
+        "ASSIGNER": "cve@mitre.org",
+        "ID": "CVE-2019-16667",
+        "STATE": "PUBLIC"
+    },
+    "affects": {
+        "vendor": {
+            "vendor_data": [
+                {
+                    "product": {
+                        "product_data": [
+                            {
+                                "product_name": "n/a",
+                                "version": {
+                                    "version_data": [
+                                        {
+                                            "version_value": "n/a"
+                                        }
+                                    ]
+                                }
+                            }
+                        ]
+                    },
+                    "vendor_name": "n/a"
+                }
+            ]
+        }
+    },
+    "data_format": "MITRE",
+    "data_type": "CVE",
+    "data_version": "4.0",
+    "description": {
+        "description_data": [
+            {
+                "lang": "eng",
+                "value": "diag_command.php in pfSense 2.4.4-p3 allows CSRF via the txtCommand or txtRecallBuffer field, as demonstrated by executing OS commands. This occurs because csrf_callback() produces a \"CSRF token expired\" error and a Try Again button when a CSRF token is missing."
+            }
+        ]
+    },
+    "problemtype": {
+        "problemtype_data": [
+            {
+                "description": [
+                    {
+                        "lang": "eng",
+                        "value": "n/a"
+                    }
+                ]
+            }
+        ]
+    },
+    "references": {
+        "reference_data": [
+            {
+                "refsource": "MISC",
+                "name": "https://pastebin.com/TEJdu9LN",
+                "url": "https://pastebin.com/TEJdu9LN"
+            }
+        ]
+    }
+}
\ No newline at end of file
diff --git a/2019/16xxx/CVE-2019-16759.json b/2019/16xxx/CVE-2019-16759.json
index 017306b4e0f..9251711f85f 100644
--- a/2019/16xxx/CVE-2019-16759.json
+++ b/2019/16xxx/CVE-2019-16759.json
@@ -66,6 +66,11 @@
                 "refsource": "MISC",
                 "name": "https://arstechnica.com/information-technology/2019/09/public-exploit-code-spawns-mass-attacks-against-high-severity-vbulletin-bug/",
                 "url": "https://arstechnica.com/information-technology/2019/09/public-exploit-code-spawns-mass-attacks-against-high-severity-vbulletin-bug/"
+            },
+            {
+                "refsource": "MISC",
+                "name": "http://packetstormsecurity.com/files/154623/vBulletin-5.x-0-Day-Pre-Auth-Remote-Command-Execution.html",
+                "url": "http://packetstormsecurity.com/files/154623/vBulletin-5.x-0-Day-Pre-Auth-Remote-Command-Execution.html"
             }
         ]
     }