dbcve.org
GlossaryWordPress extension · Codeat

CVE-2023-24378

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-06
Fix available
A fix is available. Upgrade to 2.1.28 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Codeat Glossary plugin <= 2.1.27 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 confidence

Authenticated contributor-level users can inject malicious JavaScript via the Codeat Glossary plugin's input fields. The vulnerability is a stored XSS flaw where the payload persists in the database and executes when other users view the affected content, potentially compromising admin sessions or defacing pages.

MitigationUpdate the Codeat Glossary plugin to version 2.1.28 or later, which includes proper input sanitization and output escaping. Until updated, restrict contributor-level user creation and monitor for suspicious content.

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
GlossaryWordPress extension
Affected:< 2.1.28

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Codeat Glossary plugin is installed
    Check your WordPress plugins directory or admin panel for the Codeat Glossary plugin presence
    Affected if The plugin is installed and active in the WordPress environment
  2. Determine installed plugin version
    Access the WordPress admin under Plugins > Installed Plugins and locate the Codeat Glossary entry to view its version number, or check the plugin header in its main PHP file
    Affected if The installed version is lower than 2.1.28
  3. Identify contributor-level user accounts
    Navigate to Users > All Users in the WordPress admin and filter or check for users with the Contributor role
    Affected if One or more contributor-level accounts exist in the WordPress installation
  4. Inspect glossary entries for suspicious content
    Access the Codeat Glossary admin section and review all glossary terms for unusual script tags, event handlers, or encoded JavaScript payloads in title or definition fields
    Affected if Glossary entries contain unescaped HTML or JavaScript code that could execute in a browser

The environment is affected if Codeat Glossary plugin version is below 2.1.28 and contributor-level users have access to create or edit glossary entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.1.28 or later
Fixed in 2.1.28
Interim mitigation

Update the Codeat Glossary plugin to version 2.1.28 or later, which includes proper input sanitization and output escaping. Until updated, restrict contributor-level user creation and monitor for suspicious content.

Recommended fix High confidence

Codeat Glossary version 2.1.28

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Codeat Glossary plugin in the list
  4. 4. If an update to version 2.1.28 is available, click 'Update Now' to install the patched version
  5. 5. Alternatively, you can manually update by downloading version 2.1.28 from the WordPress plugin repository or Codeat's official source
  6. 6. After updating, verify the plugin is running version 2.1.28 or higher in the Plugins list
  7. 7. Test the glossary functionality to ensure the update did not break existing features
  8. 8. Clear any caching plugins if applicable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glossary Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24378 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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