Awesomemotive Charitable cross-site request forgery in plugin request handling
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.15.2
- Who is exposed
- Not reported
Summary
The Charitable plugin for WordPress from Awesomemotive has a cross-site request forgery flaw that lets an attacker remotely, without logging in, make a user's browser perform unwanted actions on the site. The attack only works if a user is tricked into taking a step such as visiting a malicious page, and it can make limited changes to the site's data.
Written by a model
Original description
Cross-Site Request Forgery (CSRF) vulnerability in Awesomemotive Charitable charitable allows Cross Site Request Forgery.This issue affects Charitable: from n/a through 1.8.15.1.
What to do
Upgrade to a fixed version: 1.8.15.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131716 (WordPress Charitable plugin <= 1.8.15.1 - Cross Site Request Forgery (CSRF) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131716 (entry last updated 2026-11-20):
Affected:
- Awesomemotive Charitable: fixed in 1.8.15.2
Fixed versions: 1.8.15.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131716 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131716 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/charitable/vulnerability/wordpress-charitable-plugin-1-8-15-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131716
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131716"}.Affected versions
- charitablefixed in 1.8.15.2 · through 1.8.15.1
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131716 |
| Record | NVD · CVE-2026-131716 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/charitable/vulnerability/wordpress-charitable-plugin-1-8-15-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve |
Questions about CVE-2026-131716
Is CVE-2026-131716 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131716?
charitable: through 1.8.15.1 (fixed in 1.8.15.2).
Source: cve.now feed data
How do I fix CVE-2026-131716?
Upgrade to a fixed version: 1.8.15.2.
Source: cve.now feed data
Related
- CVE-2026-9059NextGEN Gallery - SQL Injection
- CVE-2026-42638WordPress Easy Digital Downloads plugin <= 3.7.1 - Broken Access Control vulnerability
- CVE-2026-48835WordPress Contact Form by WPForms plugin <= 1.10.0.4 - Broken Access Control vulnerability
- CVE-2026-39503WordPress Easy Digital Downloads plugin <= 3.6.5 - Broken Access Control vulnerability
- CVE-2026-54851WordPress Contact Form by WPForms plugin <= 2.0.3 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-54190WordPress Envira Photo Gallery plugin <= 1.12.5 - Broken Access Control vulnerability
No corrections so far. Something wrong on this page? Report an error.