CVE-2026-28761
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 request forgery vulnerability exists in Musetheque V4 Information Disclosure for IPKNOWLEDGE V4L1 rev2203.0 and earlier. If a user views a malicious page while logged-in to the affected product, unexpected operations may be done.
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 request forgery (CSRF) vulnerability in Musetheque V4 allows attackers to craft malicious pages that, when visited by authenticated users, can trigger unintended operations on the affected IPKNOWLEDGE V4L1 application due to missing or insufficient anti-CSRF protections on state-changing requests.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify if Musetheque V4 / IPKNOWLEDGE V4L1 is installedCheck running processes, deployed applications, or installed packages for references to Musetheque V4 or IPKNOWLEDGE V4L1. Inspect web server configurations, application directories, or service listings.Affected if The Musetheque V4 or IPKNOWLEDGE V4L1 application is found running in the environment
-
Determine the installed version of Musetheque V4Check application metadata files, version banners, or configuration files for the exact version number. Compare against any available version documentation.Affected if The installed version is Musetheque V4 (any version) and the application handles state-changing requests
-
Inspect state-changing endpoints for anti-CSRF token presenceReview the HTML forms or API endpoints that perform state-changing operations (such as data creation, modification, or deletion). Examine the HTML source or API request structure to determine if anti-CSRF tokens are included in the requests.Affected if State-changing endpoints lack anti-CSRF tokens in their request parameters or headers
-
Verify Origin or Referer header validationCapture a state-changing request using a proxy or browser dev tools, then attempt to send the request with a mismatched or missing Origin/Referer header. Alternatively, inspect server-side code or configuration for Origin/Referer validation logic.Affected if The application accepts state-changing requests without validating the Origin or Referer headers
-
Check SameSite cookie attributes on session cookiesInspect the Set-Cookie headers or cookie definitions in the application configuration. Look for the SameSite attribute on authentication or session cookies.Affected if Session cookies lack the SameSite attribute or have it set to None without Secure flag
The environment is affected if Musetheque V4 or IPKNOWLEDGE V4L1 is running and any state-changing endpoints lack anti-CSRF tokens, do not validate Origin/Referer headers, or use cookies without proper SameSite attributes.
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 dataImplement anti-CSRF tokens or SameSite cookie attributes on all state-changing endpoints, and validate the Origin/Referer headers to prevent cross-site request forgery attacks.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28761 — 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-28761 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