diff --git a/nuclei-templates/cve-less/plugins/wp-datepicker-a0a3a939de82e147fd84bf12ef7cefef.yaml b/nuclei-templates/cve-less/plugins/wp-datepicker-a0a3a939de82e147fd84bf12ef7cefef.yaml
new file mode 100644
index 0000000000..0a77014354
--- /dev/null
+++ b/nuclei-templates/cve-less/plugins/wp-datepicker-a0a3a939de82e147fd84bf12ef7cefef.yaml
@@ -0,0 +1,59 @@
+id: wp-datepicker-a0a3a939de82e147fd84bf12ef7cefef
+
+info:
+  name: >
+    WP Datepicker <= 2.1.4 - Reflected Cross-Site Scripting
+  author: topscoder
+  severity: medium
+  description: >
+    
+  reference:
+    - https://github.com/topscoder/nuclei-wordfence-cve
+    - https://www.wordfence.com/threat-intel/vulnerabilities/id/b6b61731-ded2-4ac1-83f6-686daf92441e?source=api-scan
+  classification:
+    cvss-metrics: 
+    cvss-score: 
+    cve-id: 
+  metadata:
+    fofa-query: "wp-content/plugins/wp-datepicker/"
+    google-query: inurl:"/wp-content/plugins/wp-datepicker/"
+    shodan-query: 'vuln:'
+  tags: cve,wordpress,wp-plugin,wp-datepicker,medium
+
+http:
+  - method: GET
+    redirects: true
+    max-redirects: 3
+    path:
+      - "{{BaseURL}}/wp-content/plugins/wp-datepicker/readme.txt"
+
+    extractors:
+      - type: regex
+        name: version
+        part: body
+        group: 1
+        internal: true
+        regex:
+          - "(?mi)Stable tag: ([0-9.]+)"
+
+      - type: regex
+        name: version
+        part: body
+        group: 1
+        regex:
+          - "(?mi)Stable tag: ([0-9.]+)"
+
+    matchers-condition: and
+    matchers:
+      - type: status
+        status:
+          - 200
+
+      - type: word
+        words:
+          - "wp-datepicker"
+        part: body
+
+      - type: dsl
+        dsl:
+          - compare_versions(version, '<= 2.1.4')
\ No newline at end of file