Table Of Contents PlusWordPress extension · Dublue
CVE-2023-44473
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 Michael Tran Table of Contents Plus plugin <= 2302 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 Table of Contents Plus WordPress plugin (versions <= 2302) allows remote attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or executing administrative functions via crafted requests.
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
Table Of Contents PlusWordPress extension
<= 2302CVSS 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.
-
Check if Table of Contents Plus plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Table of Contents Plus' or 'TOC+', or inspect the file path /wp-content/plugins/table-of-contents-plus/ for existenceAffected if Plugin is not found in the WordPress installation
-
Check the installed version numberIn WordPress admin plugins list, find the Table of Contents Plus entry and note the version number displayed below the plugin name, or open the main plugin file (table-of-contents-plus/toc.php) and check the 'Version' header in the plugin comment blockAffected if Version number is 2302 or lower (e.g., 2301, 2300, etc.)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the Table of Contents Plus plugin shows as 'Active' under the plugin statusAffected if Plugin is activated and in use on the site
If Table of Contents Plus is installed, active, and version 2302 or lower, the site is vulnerable to CVE-2023-44473 when an authenticated administrator is tricked into clicking a crafted malicious link.
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 · scopedImplement anti-CSRF tokens (nonces) for all state-changing operations including plugin settings forms and AJAX endpoints, and validate the request origin/referer header.
Table of Contents Plus version 2303 or latest available version
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Table of Contents Plus' in the plugin list
- If an update is available, click 'Update Now' to upgrade to the latest version
- After updating, verify the plugin is running version 2303 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Table Of Contents Plus
Scoped from the published advisory
- Consultation1.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44473 — 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-44473 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