CVE-2026-30457
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 · uneditedAn issue in the /parser/dwoo component of Daylight Studio FuelCMS v1.5.2 allows attackers to execute arbitrary code via crafted PHP code.
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 · high confidenceThis is a remote code execution vulnerability in the Dwoo templating parser component of FuelCMS v1.5.2. Attackers can inject and execute arbitrary PHP code by sending crafted malicious input to the /parser/dwoo endpoint, achieving full system compromise.
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= 1.1.0= 1.5.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installed FuelCMS versionCheck the FuelCMS version file or admin dashboard about page. Common locations include a version.php file in the fuel/application/config directory or the CMS admin interface.Affected if The installed version is exactly 1.5.2 (exact match required)
-
Identify installed Dwoo versionCheck the Dwoo library version included with the installation, typically found in fuel/modules/parser/libraries/dwoo or within composer/vendor directories.Affected if The Dwoo version is exactly 1.1.0 (exact match required)
-
Verify /parser/dwoo endpoint is accessibleAttempt to access the /parser/dwoo URI path on the web server (e.g., http://target.com/parser/dwoo). Check if the application routes this request to the Dwoo parser component.Affected if The endpoint responds and processes template input (even if returning an error, the route exists)
-
Confirm Dwoo parser module is enabledCheck FuelCMS parser configuration files (typically in fuel/application/config/parser.php or similar) to verify the Dwoo parser driver is loaded and enabled.Affected if The Dwoo parser driver is listed as enabled in the parser configuration
A user is affected if they run FuelCMS version 1.5.2 with Dwoo version 1.1.0 and have the /parser/dwoo endpoint accessible and enabled in their configuration.
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 dataImmediately restrict or disable the /parser/dwoo endpoint if unused, apply any available vendor patches, or upgrade to a patched version of FuelCMS; implement strict input validation on the parser if the functionality is required.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30457 — 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-2026-30457 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