CVE-2026-31205
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 · uneditedCross Site Scripting vulnerability in Pluck CMS before v.4.7.21dev allows a remote attacker to escalate privileges via the editpage.php and the sanitizePageContent function
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 confidenceCross Site Scripting (XSS) vulnerability in Pluck CMS versions prior to 4.7.21dev allows remote attackers to inject malicious scripts through the editpage.php component via the sanitizePageContent function, potentially enabling privilege escalation from lower-privileged users to higher access levels.
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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
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.
-
Verify Pluck CMS installationLocate the Pluck CMS installation by searching for core files such as index.php, install.php, or the 'pluck' directory in the web root.Affected if Pluck CMS is not present on the server, the vulnerability does not apply.
-
Determine installed Pluck CMS versionCheck the version number in the source code, typically found in a version.php file, a config file, or the main index.php. Compare it against the vulnerable range (prior to 4.7.21dev).Affected if The installed version is 4.7.20 or earlier, or any version prior to 4.7.21dev.
-
Confirm editpage.php exists and is accessibleLocate the editpage.php file within the installation directory structure, typically under the admin or includes folders. Verify the file is present and readable via the web server.Affected if The editpage.php file exists and is accessible via HTTP/HTTPS requests.
-
Inspect sanitizePageContent functionOpen editpage.php and locate the sanitizePageContent function definition. Check whether it performs proper input validation and output encoding to neutralize XSS vectors.Affected if The sanitizePageContent function exists but lacks sufficient input validation or output encoding, allowing script injection.
-
Verify low-privileged user accessConfirm that lower-privileged users (such as standard users or editors) have access to the editpage.php component to create or modify pages.Affected if Lower-privileged users can access editpage.php to inject malicious scripts and potentially escalate privileges.
A user is affected if Pluck CMS versions prior to 4.7.21dev are installed, editpage.php with a vulnerable sanitizePageContent function is accessible, and lower-privileged users can access the page editing functionality.
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 Pluck CMS to version 4.7.21dev or later; if immediate upgrade is not feasible, implement robust input validation and output encoding in the sanitizePageContent function within editpage.php to neutralize XSS vectors.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31205 — 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-31205 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