CVE-2025-28993
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Jose Mortellaro Content No Cache content-no-cache allows Code Injection.This issue affects Content No Cache: from n/a through <= 0.1.4.
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 confidenceCode injection vulnerability in the Content No Cache WordPress plugin (versions <= 0.1.4) allows remote attackers to inject and execute arbitrary code due to improper control of code generation. The plugin fails to properly sanitize user inputs before incorporating them into dynamically generated code, enabling injection attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 the Content No Cache plugin is installedLog in to the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Content No Cache' in the list of active or installed plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status
-
Check the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins. Click on 'View details' or view the plugin file header in wp-content/plugins/content-no-cache/content-no-cache.php to find the version number.Affected if The version listed is 0.1.4 or lower, or if no version is displayed and the plugin was installed prior to any patch release
-
Identify plugin entry points that generate codeInspect the main plugin file (content-no-cache.php) and look for functions that output or generate PHP code, particularly any that incorporate user input, request parameters, or dynamic values into code strings.Affected if The plugin contains code generation functions that accept unsanitized input from HTTP requests or WordPress options/settings
-
Test for unauthenticated parameter injectionReview the plugin source code for $_GET, $_POST, or $_REQUEST usage where input flows directly into generated code without sanitization functions like esc_html(), sanitize_text_field(), or prepare() for database queries.Affected if The plugin processes and incorporates raw input from request parameters into dynamically generated PHP code without proper escaping or validation
A user is affected if the Content No Cache plugin is installed with version 0.1.4 or lower and the plugin generates code using unsanitized user-controlled input.
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 dataUpgrade to the latest version of Content No Cache plugin immediately. If no patched version is available, remove the plugin entirely and seek an alternative caching control solution. Audit the codebase for improper use of eval(), dynamic code construction, or unsanitized input handling.
- 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-2025-28993 — 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-2025-28993 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