Wp TimeticsWordPress extension · Arraytics
CVE-2024-43923
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in Arraytics Timetics allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Timetics: from n/a through 1.0.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing Authorization vulnerability in Arraytics Timetics allows unauthenticated or unauthorized users to access functionality not properly constrained by Access Control Lists (ACLs). The vulnerability affects all versions up to and including 1.0.23, enabling attackers to bypass ACL mechanisms and reach protected functionality without proper authorization checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp TimeticsWordPress extension
< 1.0.24CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Timetics plugin is installedCheck your WordPress installation's wp-content/plugins directory for a folder named 'timetics', 'wp-timetics', or similar Timetics-related plugin folder. You can also list installed plugins via WordPress admin under Plugins > Installed Plugins.Affected if The Timetics plugin folder exists in the WordPress plugins directory
-
Determine installed plugin versionOpen the main plugin file (usually timetics.php or similar) and locate the 'Version' header in the plugin comment block at the top. Alternatively, check the version declared in the plugin's main PHP file.Affected if The version number found is less than 1.0.24 (for example: 1.0.23, 1.0.22, etc.)
-
Confirm plugin is activeLog in to WordPress admin and check if the Timetics plugin appears in the list of active plugins, or query the wp_options table for the option_name containing 'active_plugins'.Affected if The plugin is installed and activated on the WordPress site
You are affected if the Timetics (Wp Timetics) WordPress plugin is installed, active, and running a version earlier than 1.0.24, as this version range contains the missing authorization vulnerability that allows unauthenticated access to ACL-protected functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.0.24
Update Timetics to the latest patched version that addresses this authorization vulnerability. If no patch is available, implement proper authorization checks on all sensitive endpoints and functionality, enforcing role-based access controls consistent with ACL constraints.
1.0.24
- Backup your WordPress site database and files before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find 'Timetics' in the plugin list
- Click 'Update now' on the Timetics plugin to update to version 1.0.24
- Verify the plugin updated successfully to version 1.0.24
- Test appointment booking and calendar functionality to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Timetics
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43923 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data