CVE-2020-20627: The includes/gateways/stripe/includes/admin/admin-actions.php in GiveWP plugin through 2.5.9 for WordPress allows unauthenticated settings change.

PriorityP278medium5.3CVSS 3.1

AVNACLPRNUINSUCNILAN

ITWEXPLOITVulnCheck KEV

Exploited in the wild

EPSS

1.88%

76.9th percentile

The includes/gateways/stripe/includes/admin/admin-actions.php in GiveWP plugin through 2.5.9 for WordPress allows unauthenticated settings change.

Affected

1 ranges

Vendor	Product	Version range	Fixed in
givewp	givewp	<= 2.5.9	—

Detection & IOCsextracted from sources · hover to see the quote

url/wp-admin/admin-post.php?page=give-settings&stripe_publishable_key={{stripe_publishable_key}}&stripe_publishable_key_test={{stripe_publishable_key_test}}&stripe_user_id={{stripe_user_id}}&stripe_access_token={{stripe_access_token}}&stripe_access_token_test={{stripe_access_token_test}}&connected=1↗

pathincludes/gateways/stripe/includes/admin/admin-actions.php↗

→Exploit is a unauthenticated GET request to /wp-admin/admin-post.php with page=give-settings and Stripe credential parameters; no authentication required. ↗
→Successful exploitation confirmed when the settings-update response returns HTTP 200 with empty body (len(body) == 0), followed by the homepage reflecting the injected stripe_user_id value in the JSON key 'stripe_account_id'. ↗
→Post-exploitation verification: scan the homepage body for the strings '"base_country":', '"stripe_card_update":', and '"stripe_account_id":"<injected_value>"' to confirm settings were written. ↗
→Shodan dork to identify potentially vulnerable hosts: http.html:"/wp-content/plugins/give/" ↗
→FOFA dork to identify potentially vulnerable hosts: body="/wp-content/plugins/give/" ↗
→PublicWWW dork to identify potentially vulnerable hosts: "wp-content/plugins/give" ↗

·Vulnerability affects GiveWP plugin versions through 2.5.9 only; patched versions are not affected. ↗
·The exploit is intrusive — it actively overwrites live Stripe settings (publishable key, access token, user ID) on the target site; use only in authorized testing environments. ↗
·The detection template requires two sequential HTTP requests: the first performs the settings write, and the second verifies the change on the homepage; both must succeed for a confirmed positive. ↗

CVSS provenance

nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N

vulncheck5.3MEDIUM

CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.