CVE-2024-54369
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 ThemeHunk Zita Site Builder ai-site-builder allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Zita Site Builder: from n/a through <= 1.0.2.
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 confidenceThe Zita Site Builder plugin (ai-site-builder component) from ThemeHunk contains a Missing Authorization vulnerability (CWE-862) that allows unauthenticated or unauthorized users to access functionality that should be restricted by Access Control Lists (ACLs). This critical flaw (CVSS 9.1) affects all versions up to and including 1.0.2, potentially allowing attackers to perform privileged operations without proper authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm Zita Site Builder plugin is installedNavigate to WordPress admin > Plugins and look for 'Zita Site Builder' or 'ai-site-builder' in the plugin list, or check the /wp-content/plugins/ directory for the ai-site-builder folderAffected if The plugin folder ai-site-builder exists in the plugins directory
-
Identify the installed plugin versionIn WordPress admin > Plugins, click on the plugin name to view details, or open /wp-content/plugins/ai-site-builder/ai-site-builder.php and look for the 'Version' header in the plugin comment blockAffected if The version listed is 1.0.2 or lower (all versions up to and including 1.0.2 are affected)
-
Check for exposed AJAX actions without authorizationExamine the plugin's main PHP file and any included PHP files for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks). Look for sensitive operations like database modifications, user management, or site content changes registered with wp_ajax_nopriv_ or missing current_user_can() checksAffected if AJAX actions are registered with wp_ajax_nopriv_ or lack capability checks like current_user_can() before executing sensitive operations
-
Test unauthenticated access to admin functionsAttempt to access plugin admin pages or functions directly via URL without being logged in, or use a tool like curl to send requests to plugin AJAX endpoints without authentication cookiesAffected if Requests to plugin functions complete successfully without authentication or authorization verification
If the Zita Site Builder plugin version is 1.0.2 or lower and sensitive AJAX actions or admin functions are accessible without authentication, the environment is affected by this vulnerability.
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.
From vendor dataUpgrade Zita Site Builder to the latest version once a patch is available. If no vendor patch exists, implement manual authorization checks (current_user_can() or capability verification) on all sensitive AJAX actions and admin functions within the plugin.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54369 — 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-54369 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