CVE-2023-24384
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in WpDevArt Organization chart <= 1.4.4 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WpDevArt Organization chart WordPress plugin versions 1.4.4 and below allows attackers to induce authenticated administrators to perform unintended actions by tricking them into clicking malicious links or visiting crafted pages.
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<= 1.4.4CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm the WpDevArt Organization Chart plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins, or check the wp-content/plugins/ directory for a folder named 'organization-chart' or similar containing 'wpdevart' in the nameAffected if The plugin appears in the installed plugins list in any state (active or inactive)
-
Identify the installed version numberIn WordPress admin, find the plugin in the plugins list and note the version number displayed beneath the plugin name, or open the plugin's main PHP file (usually in wp-content/plugins/[plugin-folder]/[plugin-name].php) and look for the 'Version:' header in the plugin comment blockAffected if The version number is 1.4.4 or lower, or if no version is displayed and the plugin was installed prior to any patches
-
Verify administrator access existsConfirm that administrator-level accounts exist on the WordPress site, as CVE-2023-24384 requires a logged-in administrator to be tricked into an actionAffected if There are active administrator accounts that could be targeted for CSRF attacks through the plugin's admin interfaces
-
Identify state-changing operations in the pluginExamine the plugin's admin pages and AJAX endpoints for forms that perform actions (such as creating, editing, or deleting organization chart data, or modifying plugin settings) - check if these forms include nonce fields or CSRF tokensAffected if The plugin contains forms or AJAX handlers that process requests without validating a nonce or CSRF token, which would be confirmed through code review or functional testing of the plugin's admin actions
A user is affected if they have WpDevArt Organization Chart plugin installed with version 1.4.4 or lower and the plugin processes administrative actions without CSRF protection.
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 dataImplement WordPress nonce validation on all state-changing operations (forms and AJAX endpoints) and add CSRF tokens to plugin pages; users should update to a patched version once released.
- 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-2023-24384 — 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-2023-24384 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