League TableWordPress extension · Daext
CVE-2023-48334
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 DAEXT League Table allows Cross Site Request Forgery.This issue affects League Table: from n/a through 1.13.
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 DAEXT League Table WordPress plugin allows remote attackers to induce authenticated administrators into unknowingly executing unintended actions via crafted requests, as the plugin lacks proper anti-CSRF token validation on state-changing operations.
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
League TableWordPress extension
<= 1.13CVSS 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 the DAEXT League Table plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'Daext League Table' in the list of active or installed pluginsAffected if The plugin appears in the installed plugins list regardless of activation status
-
Check the installed plugin versionClick on the plugin in the WordPress plugins list to view its details, or check the plugin's main PHP file header for the 'Version' tag in the plugin metadataAffected if The displayed version number is 1.13 or any lower version number
-
Inspect admin forms for nonce fieldsView the source code of any admin-facing forms created by the plugin (such as settings pages, table creation/editing forms) and search for wp_nonce_field() or similar WordPress nonce generation functionsAffected if Forms lack nonce fields or have nonce fields that are not validated on submission
-
Inspect AJAX actions for nonce verificationExamine the plugin's AJAX handlers (typically in main PHP files or dedicated ajax directory) and verify that each handler calls check_ajax_referer() or wp_verify_nonce() before processing requestsAffected if AJAX actions process requests without verifying a nonce token first
-
Check state-changing operations for CSRF protectionReview any PHP functions in the plugin that perform database writes (create, update, delete operations on tables, options, or custom post types) and verify they validate a nonce before executingAffected if State-changing functions execute without prior nonce validation
If the DAEXT League Table plugin version 1.13 or lower is installed AND the plugin lacks proper nonce validation on its admin forms and AJAX actions, the environment is vulnerable to CVE-2023-48334.
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 nonces (nonce verification) for all forms and AJAX actions within the plugin to ensure requests originate from legitimate admin sessions.
Fix this in League Table
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-48334 — 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-48334 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