CVE-2025-52756
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 Sayan Datta WP Last Modified Info wp-last-modified-info allows Remote Code Inclusion.This issue affects WP Last Modified Info: from n/a through <= 1.9.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 confidenceA code injection vulnerability in the WP Last Modified Info WordPress plugin (versions up to 1.9.4) allows remote code inclusion due to improper control of code generation. An attacker can potentially inject and execute malicious code on the server through this vulnerability.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
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.
-
Locate the plugin installation directoryAccess your WordPress site's wp-content/plugins/ directory and check for a folder named 'wp-last-modified-info'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to find WP Last Modified Info in the list.Affected if The plugin folder or listing exists on the WordPress installation
-
Determine the installed plugin versionIn the WordPress admin, find WP Last Modified Info in the Plugins list and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (wp-last-modified-info/prefix-wplmi-main.php or similar) in the plugins directory and look for the 'Version' header in the file comments.Affected if The version number found is 1.9.4 or any lower version number
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and check if WP Last Modified Info shows as 'Active' (not deactivated or deleted).Affected if The plugin is active with a vulnerable version (1.9.4 or below)
-
Check for unauthorized code modificationsCompare the plugin files against a clean installation of the same version. Look for unexpected .php files in the plugin directory, base64-encoded strings in existing files, or newly added files with suspicious names (e.g., shell scripts, encoded payloads).Affected if Unexpected or malicious files are present in the plugin directory indicating exploitation
Your environment is affected if the WP Last Modified Info plugin is installed, active, and the version is 1.9.4 or lower.
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 WP Last Modified Info plugin to the latest version that addresses this code injection vulnerability. If no patch is available, consider disabling the plugin until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52756 — 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-52756 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