Simple Org ChartWordPress extension · Webtechforce
CVE-2023-40008
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 Gangesh Matta Simple Org Chart plugin <= 2.3.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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Gangesh Matta Simple Org Chart WordPress plugin affecting versions 2.3.4 and earlier. CSRF attacks exploit the trust a web application places in an authenticated user's browser by tricking it into sending malicious requests without the user's knowledge. An attacker could potentially perform unauthorized actions on behalf of a logged-in administrator or user.
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
Simple Org ChartWordPress extension
<= 2.3.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.
-
Verify Simple Org Chart plugin is installedCheck WordPress wp-admin under Plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'simple-org-chart' or 'webtechforce'Affected if The Simple Org Chart plugin by Webtechforce is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the version listed for Simple Org Chart, or open the main plugin PHP file (e.g., simple-org-chart.php) and check the 'Version' header in the plugin comment blockAffected if The displayed version is 2.3.4 or lower (e.g., 2.3.4, 2.3.3, 2.3.0, 1.0, etc.)
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify the Simple Org Chart plugin shows as 'Active'Affected if The plugin is currently activated on the WordPress site
-
Identify state-changing operationsReview plugin source code for form actions or AJAX endpoints that perform create/update/delete operations (POST/DELETE requests) and check if they include anti-CSRF tokens (wp_nonce_field, check_admin_referer, or similar nonce verification)Affected if The plugin performs administrative or user actions without verifying anti-CSRF tokens
If Simple Org Chart plugin version 2.3.4 or earlier is installed and active, and the plugin handles state-changing requests without CSRF token validation, the environment is vulnerable to CVE-2023-40008.
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 dataUpdate the Simple Org Chart plugin to the latest version once a patch is available, or implement anti-CSRF tokens on all state-changing operations (POST/DELETE requests) within the plugin.
Fix this in Simple Org Chart
Scoped from the published advisory
- 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-40008 — 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-40008 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