Is Bulk Datetime Change safe?

No known vulnerability affects the current version (2.00). 1 issue was found in earlier versions and fixed, the latest disclosed on Oct 26, 2021.

Checked 2 days ago against the WPVulnerability database, for version 2.00.

How it’s looked after

Last release: Oct 19, 2026 (2 weeks ago)
Releases in the last year: 3
Tested up to: WordPress 7.1.4
Active installs: 6K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in Bulk Datetime Change

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

medium
Missing Authorisation
Fixed in 1.12 · CVE-2021-24842 · Oct 26, 2021 · Wordfence

Questions about Bulk Datetime Change’s security

Is Bulk Datetime Change safe to use?

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

Does Bulk Datetime Change have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Bulk Datetime Change up to date.

Is Bulk Datetime Change still maintained?

Yes. Its last release was 2 weeks ago. No support threads were opened in the last two months.

Is Bulk Datetime Change 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.