
Unofficial community security backport for Booked 2.4.4, mitigating CVE-2026-22341, CVE-2026-57746 and CVE-2026-57747.
Unofficial community security backport for Booked – Appointment Booking for WordPress 2.4.4.
This repository does not distribute the original Booked plugin package. It provides a patch intended to be applied to a legitimately obtained Booked 2.4.4 installation.
Release: 2.4.4.2-14h28-security-backport
Security backport author / maintainer: Zied El Ifa
Contact: [email protected]
The backport was created to mitigate publicly disclosed Booked vulnerabilities and to port relevant security hardening documented by QuickCal. It has been statically reviewed, syntax-checked, and manually regression-tested on a real WordPress installation.
This is an unofficial mitigation, not an upstream Booked/QuickCal release and not a guarantee that no undiscovered vulnerabilities exist.
The backport targets the following publicly disclosed issues:
It also backports security hardening matching the relevant QuickCal changelog work through v1.0.23, including:
QuickCal has continued evolving after v1.0.23. This project is a compatibility/security backport for sites that cannot immediately migrate; it is not a replacement for moving to a maintained booking plugin.
patch, or another patching workflow capable of applying unified diffs.From wp-content/plugins (the directory that contains the booked/ folder):
cp -a booked booked.backup-before-security-backport
patch --dry-run -p1 \
< /path/to/booked-2.4.4.2-14h28-security-backport.patch
patch -p1 \
< /path/to/booked-2.4.4.2-14h28-security-backport.patch
Then clear WordPress/server/page caches.
The plugin header should report:
Version: 2.4.4.2
Description: ... (14h28 Security Backport)
The patch replaces legacy 32-character iCalendar feed tokens with a 64-character cryptographically generated token.
After first load, if you use external calendar subscriptions, retrieve the new feed URL from:
Appointments / Rendez-vous → Settings / Paramètres → Calendar Feeds
Update Outlook, Apple Calendar, Google Calendar, or any external consumer that still uses the old feed URL.
Wordfence, Patchstack, or other scanners may continue flagging the plugin because they identify the public Booked package/slug and upstream version range. This community patch does not change upstream vulnerability databases.
Do not fake a version such as 3.0.1 merely to hide scanner alerts. Keep the explicit backport version and document the local mitigation.
The backport was manually validated for:
See docs/TESTING.md for a reusable checklist.
patches/booked-2.4.4.2-14h28-security-backport.patch — patch to apply to Booked 2.4.4.docs/SECURITY.md — security scope and disclosure policy.docs/TESTING.md — manual regression/security test matrix.docs/CHANGELOG.md — backport changelog.docs/REFERENCES.md — public advisories and upstream changelog references.docs/SOURCE-FINGERPRINT.md — SHA-256 of the specific Booked 2.4.4 archive used during validation.scripts/preflight.sh — verifies the source version and runs a patch dry-run.The repository intentionally does not include the original Booked commercial distribution. The patch contains modifications/differences intended for use with a legally obtained copy of Booked 2.4.4.
The patch and original-project-derived modifications should be used consistently with the licensing terms applicable to Booked and WordPress-derived code. See LICENSE and NOTICE.md.
No warranty is provided. Back up first, test in staging, and monitor the installation after deployment. A maintained upstream product or migration remains preferable for long-term security.