Dw Question & Answer
Approved changes feed: RSS · Atom
cpe:2.3:a:designwall:dw_question_\&_answer:*:*:*:*:pro:wordpress:*:*
part: a version: * update: *
| Vendor | Designwall (92fb3d45-f22c-5b01-b643-5a9c88af931b) |
|---|---|
| Product | Dw Question & Answer (f88a9136-9b0a-5306-87c6-2c802290802a) |
| Edition | * |
| Language | * |
| Software edition | pro |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-4408 |
vulnerable | 2026-06-08 05:38:09.363599 |
DW Question & Answer <= 1.5.8 - Cross-Site Request Forgery Bypass
MEDIUM (4.3)
The DW Question & Answer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.8. This is due to missing or incorrect nonce validation on the update_answer() function. This makes it possible for unauthenticated attackers to update answers to questions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2023-07-12T03:02:02.414Z
Updated: 2026-04-08T17:10:39.670Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-24805 |
vulnerable | 2026-06-08 05:30:39.275905 |
DW Question & Answer Pro <= 1.3.4 - Multiple CSRF
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.
Published: 2022-04-25T15:50:43.000Z
Updated: 2024-08-03T19:42:17.212Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-24800 |
vulnerable | 2026-06-08 05:30:39.266789 |
DW Question & Answer Pro <= 1.3.4 - Arbitrary Comment Edition via IDOR
The DW Question & Answer Pro WordPress plugin through 1.3.4 does not check that the comment to edit belongs to the user making the request, allowing any user to edit other comments.
Published: 2022-04-25T15:50:41.000Z
Updated: 2024-08-03T19:42:17.205Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.