weForms · Security record

Is weForms safe?

No known vulnerability affects the current version (1.6.29). 14 issues were found in earlier versions and fixed, the latest disclosed on Oct 21, 2026.

Checked 3 days ago against the WPVulnerability database, for version 1.6.29.

How it’s looked after

Last release: Oct 16, 2026 (3 weeks ago)
Releases in the last year: 5
Tested up to: WordPress 7.1.4
Support resolved: 0 of 1 threads in two months
Active installs: 10K+

14 known vulnerabilities

2 critical
2 high
7 medium
3 not rated

None affects the current version.

Disclosed each year

20201
20221
20232
20245
20251
20264

Every known vulnerability in weForms

Newest first, with any that affect the current version at the top.

high
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Bold Grid weForms weforms allows Path Trave…
Fixed in 1.6.29 · CVE-2026-111833 · Oct 21, 2026 · CVE
medium
Unauthenticated Limited Media File Deletion via 'wpuf_files' Parameter
Fixed in 1.6.29 · CVE-2026-110253 · Mar 23, 2026 · Wordfence
high
Unauthenticated PHP Object Injection
Fixed in 1.6.27 · CVE-2026-32484 · Mar 23, 2026 · Wordfence
Authenticated (Subscriber+) Stored Cross-Site Scripting via Hidden Field Value via REST API
Fixed in 1.6.28 · CVE-2026-2707 · Mar 10, 2026 · Wordfence
medium
Missing Authorization
Fixed in 1.6.26 · CVE-2025-69028 · Dec 29, 2025 · Wordfence
WordPress weForms Plugin <= 1.6.23 is vulnerable to Backdoor
Fixed in 1.6.24 · Jul 3, 2024 · Patchstack
Use of Polyfill.io
Fixed in 1.6.24 · Jun 25, 2024 · Wordfence
medium
WordPress weForms Plugin <= 1.6.20 is vulnerable to Bypass Vulnerability
Fixed in 1.6.21 · CVE-2024-32512 · Apr 15, 2024 · Patchstack
critical
Missing Authorization
Fixed in 1.6.21 · CVE-2024-30512 · Mar 28, 2024 · Wordfence
medium
Unauthenticated Stored Cross-Site Scripting via Referer
Fixed in 1.6.22 · CVE-2024-0386 · Mar 12, 2024 · Wordfence
medium
Missing Authorization via export_form_entries
Fixed in 1.6.19 · CVE-2023-51524 · Dec 27, 2023 · Wordfence
medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 1.6.18 · CVE-2023-50896 · Dec 26, 2023 · Wordfence
medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 1.6.14 · CVE-2022-2395 · Jul 12, 2022 · Wordfence
critical
CSV injection via form entry
Fixed in 1.6.4 · CVE-2020-22276 · Aug 13, 2020 · Wordfence

Questions about weForms’s security

Is weForms safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep weForms updated: most attacks target sites that haven’t updated.

Does weForms have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 14 older issues, fixed in earlier versions, so keep weForms up to date.

Is weForms still maintained?

Yes. Its last release was 3 weeks ago. Its authors resolved 0 of the 1 support threads opened in the last two months.

Is weForms compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.