Ce21 SuiteWordPress extension · Ce21
CVE-2024-10285
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 · uneditedThe CE21 Suite plugin for WordPress is vulnerable to sensitive information disclosure via the plugin-log.txt in versions up to, and including, 2.2.0. This makes it possible for unauthenticated attackers to log in the user associated with the JWT token.
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 · high confidenceThe CE21 Suite WordPress plugin exposes a publicly accessible log file (plugin-log.txt) that contains sensitive JWT tokens. Unauthenticated attackers can directly request this file to obtain valid JWT tokens and impersonate users on the affected site.
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
Ce21 SuiteWordPress extension
<= 2.2.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Ce21 Suite plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Ce21 Ce21 Suite'. Note the installed version number displayed.Affected if Plugin is installed and version is 2.2.0 or lower
-
Locate the exposed log fileCheck for the presence of plugin-log.txt in the web root directory (typically public_html or www/html). Attempt to access it via HTTP: http://yourdomain.com/plugin-log.txtAffected if The file plugin-log.txt exists and is publicly accessible via web request
-
Inspect log file contents for JWT tokensIf the file exists, examine its contents. Look for string patterns resembling JWT tokens (three base64-encoded sections separated by dots, such as 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...')Affected if The file contains any JWT token strings
-
Compare installed version to affected rangeCompare your installed plugin version against the affected range: version 2.2.0 or earlierAffected if Installed version is 2.2.0 or lower AND the plugin-log.txt file is present and accessible
You are affected if the Ce21 Suite plugin version is 2.2.0 or lower AND the plugin-log.txt file exists and is accessible on your web server, particularly if it contains JWT tokens.
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 dataImmediately restrict or delete the plugin-log.txt file from the web root, and update the plugin to the latest version once a patch is available.
Fix this in Ce21 Suite
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10285 — 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-10285 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