CVE-2026-40545
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 · uneditedSOPlanning is vulnerable to Reflected XSS via the taches parameter. An attacker can craft a malicious URL which, when opened by authenticated victim, results in arbitrary JavaScript execution in the victim’s browser. This issue affects SOPlanning version 1.55 and below.
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 confidenceSOPlanning versions 1.55 and below contain a reflected XSS vulnerability in the taches parameter. When an authenticated victim clicks a specially crafted URL, the unsanitized input is reflected back in the HTTP response without proper output encoding, allowing the attacker to execute arbitrary JavaScript in the victim's browser.
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
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 SOPlanning is installedCheck your web server for the SOPlanning application directory (commonly /soplanning or /wp-content/plugins/soplanning) or look for SOPlanning login pages responding on your domain.Affected if SOPlanning software is present on the server
-
Determine installed SOPlanning versionLocate the version file: typically includes/version.php, VERSION.txt, or check the footer/login page source for a version string like 'v1.55' or similar.Affected if The displayed version is 1.55 or lower (e.g., 1.55, 1.54, 1.50)
-
Confirm the 'taches' parameter is reachableCheck if the application handles requests with a 'taches' parameter - common in task management interfaces. Review application routing or PHP source files in the /taches or /task directories for parameter usage.Affected if The 'taches' parameter is processed by the application without sanitization
-
Verify authentication is required for exploitationConfirm that accessing the vulnerable endpoint requires a valid authenticated session. Attempt to access the URL without credentials to see if the parameter is processed.Affected if The vulnerability only affects authenticated users; unauthenticated access may be blocked but the flaw still exists in the authenticated code path
If SOPlanning version 1.55 or below is installed and the 'taches' parameter is functional in the application, the environment is affected by this reflected XSS vulnerability.
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 dataApply input validation and output encoding to the taches parameter, preferably using a vetted XSS prevention library. Users should avoid clicking untrusted links until the vendor releases a patch.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40545 — 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-40545 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