CVE-2025-60070
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 The4 Molla molla allows Code Injection.This issue affects Molla: from n/a through <= 1.5.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 confidenceCode injection vulnerability in The4 Molla theme (versions <= 1.5.13) allows remote attackers to inject and execute arbitrary code due to improper control of code generation. The vulnerability stems from user-supplied input being evaluated or executed without proper sanitization, potentially leading to full system compromise.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Confirm Molla theme is installedCheck your WordPress themes directory (wp-content/themes/) for the 'molla' folder. If the folder exists, the theme is installed.Affected if The molla folder exists in the themes directory.
-
Identify the installed versionOpen the file 'style.css' within the molla theme folder and locate the 'Version:' declaration in the file header. Compare this version number to the affected range (<= 1.5.13).Affected if The version listed is 1.5.13 or lower.
-
Locate code evaluation or generation functionsSearch the theme files (particularly in includes/, framework/, or similar directories) for dangerous PHP functions that execute code, such as eval(), exec(), system(), shell_exec(), preg_replace() with the /e modifier, or file operations that accept dynamic input.Affected if Any of these functions are present and process user-supplied input without sanitization.
-
Inspect input handling for code injection vectorsReview PHP files that handle user input (POST, GET, or cookie parameters) and trace whether that input flows into any code generation or evaluation functions without being sanitized or escaped.Affected if User input is passed directly to eval(), preg_replace(), or similar functions without validation.
You are affected if the Molla theme is installed with version 1.5.13 or lower AND your environment contains code evaluation or generation functions that process unsanitized user 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 dataUpdate to the latest version of the Molla theme if a patch is available. If no patch exists, implement strict input validation and sanitize all user inputs before any code generation or evaluation, and consider deploying a WAF as a temporary compensating control.
- 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-60070 — 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-60070 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