CVE-2025-46450
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 (CSRF) vulnerability in x000x occupancyplan occupancyplan allows Stored XSS.This issue affects occupancyplan: from n/a through <= 1.0.3.0.
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 the occupancyplan component allows unauthenticated attackers to trick authenticated users into submitting malicious requests that store XSS payloads within the application.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Confirm occupancyplan component presenceSearch the application codebase or deployed files for any component, module, or route named 'occupancyplan' or similar variations. Check the application's module/component listing if available.Affected if The occupancyplan component exists in the environment and is accessible to authenticated users.
-
Inspect occupancyplan forms for anti-CSRF tokensLocate all HTML forms or API endpoints within the occupancyplan component that perform state-changing operations (create, update, delete occupancy plans). Examine the form markup or request handling code to determine if a unique, session-bound anti-CSRF token is required and validated on submission.Affected if Forms in the occupancyplan component lack anti-CSRF token generation or validation logic.
-
Verify input validation on occupancyplan submissionsReview the server-side code that processes occupancyplan form submissions. Check if the application performs input validation, sanitization, or encoding on user-supplied data before storing it.Affected if The occupancyplan component accepts and stores user input without proper validation or sanitization.
-
Test for stored XSS via occupancyplanAs an authenticated user, submit a test payload (such as <script>alert(1)</script>) through the occupancyplan form. Then navigate to any page where the submitted data is displayed and observe if the payload executes without encoding.Affected if The submitted payload executes as JavaScript when the stored data is rendered in the application.
A user is affected if the occupancyplan component exists and its forms lack anti-CSRF protection, allowing attackers to inject stored XSS through authenticated users.
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 on all state-changing forms and apply proper input validation with context-aware output encoding to prevent stored XSS injection.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46450 — 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-2025-46450 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