Skip to content
Blog

Craft CMS · Craft Commerce · Grav

Craft CMS, Grav, LaraDashboard, WP Duplicate: Four Critical PHP CMS Flaws in Two Days (CVE-2026-130675, 130733, 130754, 14492)

Craft CMS RCE, Grav permission bypass, LaraDashboard account takeover, WP Duplicate RCE: four critical PHP CMS CVEs, affected versions and mitigation.

Between November 18 and 19, 2026, NVD published four critical CVEs in self-hosted PHP CMSs and admin panels: Craft CMS, Grav, LaraDashboard and the WP Duplicate WordPress plugin.

The mechanisms have nothing in common, which is what makes the batch worth reading: arbitrary class instantiation, a storage key collision, an over-trusting OAuth link, and a loose PHP comparison. Four different ways to lose control of a site.

ProductCVECVSS 3.1CVSS 4.0Flaw classNVD bounds
Craft CMSCVE-2026-1306759.89.3Code execution (CWE-697)5.0.0 → before 5.11.4
GravCVE-2026-1307339.89.3Authorization bypass (CWE-140)2.0.0 → before 2.2.18
LaraDashboardCVE-2026-1307549.89.3Authentication bypass (CWE-287)all versions
WP DuplicateCVE-2026-144929.8—Upload / code execution (CWE-434)up to and including 1.1.11

The first three scores come from VulnCheck (CNA), WP Duplicate's from Wordfence (CNA). Craft CMS is in NVD status Awaiting Analysis, the other three are Deferred. None is in CISA KEV at the time of writing.


Craft CMS — CVE-2026-130675

Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

ImageTransforms::normalizeTransform() accepts an image transform given as an array. According to NVD, passing class:null together with a __class key makes it instantiate an arbitrary class.

NVD spells out the path: Craft Commerce's payments/pay redirect template calls customer.photo.getUrl() with an attacker-controllable transform. Instantiating a class such as yii\rbac\PhpManager gives the attacker PHP execution.

Exposure: the description names Craft Commerce as the entry point. A Craft site without Commerce doesn't expose that particular path, but the vulnerable method lives in the CMS core, and nothing guarantees there's no other route to it. Upgrade either way.


Grav — CVE-2026-130733

Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Grav supports per-page permissions. NVD describes a bypass through key delimiter collisions in FolderStorage combined with folder reconstruction in PageStorage. By renaming a folder to something like locked***, or saving from a page with an unusual prefix width through a front-end Flex Pages form, an attacker overwrites a protected page, permissions included, and gains access to the whole subtree below it.

Worth noting: the vector says PR:N, but the description talks about attackers holding the publisher role. On a site where a handful of trusted editors publish, the risk is lower; on a site open to many contributors, it's real.

Grav already came up in October with its OAuth login plugin.


LaraDashboard — CVE-2026-130754

Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

LaraDashboard is a Laravel-based admin panel. SocialAuthService::findOrCreateUser() links a social login to an existing account by email address without checking that the OAuth provider actually verified that address.

Per NVD, an attacker using an OAuth/OIDC provider that asserts the victim's email can log in as any user, Superadmin included, and keep persistent access through the social_accounts entry that gets created.

NVD lists all versions as affected and names no fix: see advisory GHSA-c5x3-wvxj-7cgr.

It's a textbook social-login mistake: an email address identifies, it doesn't prove. Only the provider's "email verified" claim, and only from providers you trust on that point, justifies merging two accounts.


WP Duplicate — CVE-2026-14492

Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (Wordfence)

WP Duplicate is a WordPress migration plugin (slug local-sync). NVD describes two flaws combined in save_single_batch_file():

  • a PHP type-juggling authentication bypass: the secret key is compared with a loose != and there's no check that the value is a string;
  • a path built from a base64-decoded value with no directory traversal containment.

The result is arbitrary file writes, and so code execution on the server.

Condition: the site owner must have completed the plugin's initial setup. The description mentions authenticated attackers with custom-level access, while Wordfence's vector says PR:N; NVD adds that any non-empty secret can be bypassed through the comparison flaw.

Versions: everything up to and including 1.1.11. NVD gives no fixed version: check the plugin page before treating a release as safe.


Detection

  • Craft CMS: requests to payments/pay with transform parameters containing __class; recently created PHP files in the webroot.
  • Grav: page folders renamed with * characters; protected pages modified by a publisher account; unexpected changes to page permission headers.
  • LaraDashboard: new rows in social_accounts tied to admin accounts; social logins on accounts that never used one.
  • WP Duplicate: requests to the plugin's endpoints from unknown IPs; recent PHP files outside the expected wp-content/ folders.

Mitigation

  1. Craft CMS: move to 5.11.4 or later (first version outside the NVD range); see advisory GHSA-hq78-cm2m-h24h.
  2. Grav: move to 2.2.18 or later, see GHSA-3rxf-jpgc-hwpv; meanwhile, trim the number of publisher accounts.
  3. LaraDashboard: with no fixed version in NVD, turn off social login and audit social_accounts.
  4. WP Duplicate: deactivate and delete the plugin outside of actual migrations. A migration plugin has no reason to stay active in production.

NVD bounds give the first version outside the range, not necessarily the recommended release: each project's advisory is the reference.


Why Continuous Monitoring of Your Self-Hosted CMSs Matters

Four CMSs, four communities, four different disclosure channels (GitHub advisories, Wordfence, changelogs). Nobody tracks all of that by hand for every site they host.

With cveo.tech, inventory your CMSs, plugins and versions, and get an alert as soon as a critical CVE affects them.

Running PHP servers? Know which CVEs hit your version.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.