Show filters
74 Total Results
Displaying 41-50 of 74
Sort by:
Attacker Value
Unknown

CVE-2023-1238

Disclosure Date: March 07, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6.
Attacker Value
Unknown

CVE-2023-1237

Disclosure Date: March 07, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.6.
Attacker Value
Unknown

CVE-2023-0934

Disclosure Date: February 21, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.5.
Attacker Value
Unknown

CVE-2023-0744

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Improper Access Control in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2023-0743

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Generic in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2023-0742

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2023-0741

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - DOM in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2023-0740

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2023-0739

Disclosure Date: February 08, 2023 (last updated February 24, 2025)
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in GitHub repository answerdev/answer prior to 1.0.4.
Attacker Value
Unknown

CVE-2021-24805

Disclosure Date: April 25, 2022 (last updated February 23, 2025)
The DW Question & Answer Pro WordPress plugin through 1.3.4 does not properly check for CSRF in some of its functions, allowing attackers to make logged in users perform unwanted actions, such as update a comment or a question status.