Bulk WooCommerce Category Creator
Limited data: Bulk WooCommerce Category Creator has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Based on 3 of 5 areas
Capped at 39: a vulnerability has no patch.
| Ownership | 100 |
|---|---|
| Maintenance | 100 |
| Security | 40 |
| Support | No data |
| Reputation | No data |
Active signals
Open issues right now, with links to the source.
- CriticalSEC-2Vulnerability published 4 Mar 2022 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.18 Mar 2022Evidence
History: 2 past vulnerabilities, 1 still unpatched in the current version. Patched issues are listed in the Security record, not here.
Quick answers
- Is Bulk WooCommerce Category Creator still maintained?
- Yes. Last release 26 Oct 2026, 1 release in the last 24 months. 26 Oct 2026 · wordpress.org
- Who owns Bulk WooCommerce Category Creator, and has it changed hands?
- No change recorded. Main committer kartikparmar since May 2018. 3 Nov 2026 · SVN log
- Was Bulk WooCommerce Category Creator removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is Bulk WooCommerce Category Creator safe?
- No. 1 known vulnerability has no fix in the current version. 18 Jul 2023 · Wordfence Intelligence
- Is the latest Bulk WooCommerce Category Creator update safe to install?
- No ownership change before 2.4. No one-star spike after it. 26 Oct 2026 · Release history
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| kartikparmar | 12 May 2018 to 26 Oct 2026, 45 commits |
|---|
1 committer recorded. No ownership changes recorded since 2018.
Maintenance
- Last release
- 10 days ago
- Releases, 24 months
- 1
- Tested up to
- 7.1 current
- Requires PHP
- 7.4 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 1 |
Last release 26 Oct 2026. Tested with WordPress 7.1 (current).
Support
- Resolved, last 2 months
- 0%
- Threads, last 2 months
- 1
Trend appears after 8 weekly snapshots.
Security record
2 vulnerabilities on record, 1 with no fix in the current version.
| Date | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 4 Mar 2022 | Missing Authorization Checks | 6.3 | all | No fix | n/a |
Show 1 patched vulnerability
| Date | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 18 Jul 2023 | Reflected Cross-Site Scripting via fs_request_get | 6.1 | <= 2.3 | Not affected | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Reputation
Last 90 days: no reviews. Lifetime: 4.5.
| Last 90 days | No reviews |
|---|---|
| Lifetime | 4.5 |
| 5 star | 7 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 1 |
Momentum
- Active installs
- 400+
Trend appears after 8 weekly snapshots.
Facts
- Version
- 2.4
- Author
- kartikparmar
- Added
- 12 May 2018
- Last updated
- 26 Oct 2026
- Active installs
- 400+
- Requires WordPress
- 5.8
- Tested up to
- 7.1.4
- Requires PHP
- 7.4
- Category
- not stated
- Tags
- bulk, create, product, category, multiple
Other plugins by this author: Change Price Title for WooCommerce, Bulk Post Category Creator, Timezone Conversion Widget, Sort Products in Cart & Order Lite for
Questions about Bulk WooCommerce Category Creator
Is Bulk WooCommerce Category Creator still maintained?
Yes. Last release 26 Oct 2026, 1 release in the last 24 months.
Who owns Bulk WooCommerce Category Creator, and has it changed hands?
No change recorded. Main committer kartikparmar since May 2018.
Was Bulk WooCommerce Category Creator removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is Bulk WooCommerce Category Creator safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest Bulk WooCommerce Category Creator update safe to install?
No ownership change before 2.4. No one-star spike after it.