CVE-2025-30580
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 kellydiek DigiWidgets Image Editor digiwidgets-image-editor allows Remote Code Inclusion.This issue affects DigiWidgets Image Editor: from n/a through <= 1.10.
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 DigiWidgets Image Editor allows remote code inclusion, likely due to improper validation of user-supplied input used in file inclusion or dynamic code execution functions. The CVSS 10 score indicates trivial exploitability with total compromise potential.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Identify if DigiWidgets Image Editor is installedSearch the system for DigiWidgets Image Editor files, check web server document roots for image-editor directories, or review installed application listsAffected if DigiWidgets Image Editor is present on the system
-
Determine the installed versionCheck version files within the DigiWidgets installation directory, review composer.json, or inspect headers/response from the applicationAffected if The installed version is older than the latest available version or does not contain the security fix
-
Verify if remote file inclusion (RFI) functionality is enabledReview the application configuration files (config.php, settings.ini, or similar) for parameters controlling remote file inclusion or external resource loadingAffected if RFI or external file inclusion is permitted in the configuration
-
Inspect file inclusion code pathsExamine the source code for dynamic include(), require(), eval(), or similar functions that handle user-supplied input without sanitizationAffected if User-controlled parameters flow into file inclusion or code execution functions without proper validation
-
Check for exposed entry pointsReview HTTP parameter handling in the image editor components, particularly features that accept file paths or URLs as inputAffected if Unvalidated file path or URL parameters are accepted via GET/POST requests
The environment is affected if DigiWidgets Image Editor is installed and user-supplied input can be passed to file inclusion or dynamic code execution functions without validation.
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 dataUntil an official patch is available, implement strict allowlist-based input validation on all file inclusion parameters and disable remote file inclusion functionality; consider upgrading to the latest version if a patch is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30580 — 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-30580 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