WordPress security by component
CM Answers
Plugin description
CM Answers is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Apr 22, 2025; the highest published CVSS base score is 5.9.
Plugin slug:
cm-answersLatest vulnerability
CVE-2025-46246: CM Answers: Cross-site request forgery
CM Answers is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Apr 22, 2025 |
CVE-2025-46246
CM Answers: Cross-site request forgery
CM Answers is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Dec 13, 2024 |
CVE-2024-54267
CM Answers: A security weakness
CM Answers is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Mar 23, 2023 |
CVE-2023-25992
Cm Answers: Cross-site scripting
Cm Answers is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.9
NVD4.8
|