dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-45483

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 16.0.19725.20384 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office Project Server allows an authorized attacker to perform spoofing over a network.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Microsoft Office Project Server where improper input validation allows an authenticated attacker to inject malicious script content into web pages. When other users view these pages, the attacker's scripts execute in their browsers, enabling session hijacking, credential theft, and spoofing attacks.

MitigationApply Microsoft's security patches for this vulnerability when available. In the interim, implement output encoding and input validation on user-supplied data, and consider restricting user permissions to minimize the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sharepoint ServerApplication
Affected:< 16.0.19725.20384= 2016= 2019

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SharePoint Server version
    Open SharePoint Management Shell and run: (Get-SPFarm).BuildVersion or check Central Administration > System Settings > Manage farm configuration > Check the Build version
    Affected if The version is 16.0.19725.20384 or lower, or matches SharePoint 2016 or 2019
  2. Confirm Project Server is enabled
    In Central Administration, navigate to Application Management > Manage service applications > Verify if Project Server Service Application exists and is started. Alternatively, run: Get-SPServiceApplication | Where-Object {$_.TypeName -like '*Project*'}
    Affected if Project Server Service Application is created and running
  3. Check for unauthenticated or low-privilege access points
    Review web application authentication providers in Central Administration > Application Management > Manage web applications > Authentication Providers. Verify which zones allow anonymous access or low-privilege user access.
    Affected if Anonymous access or low-privilege user authentication is enabled on Project Server web applications
  4. Audit custom Project Server pages or web parts
    Review deployed custom solutions in SharePoint: Central Administration > System Settings > Manage farm solutions. Check Project Server sites for custom JavaScript or unencoded user input fields in Project Detail Pages (PDP) or status reports.
    Affected if Custom web parts or modified PDPs exist that display user-supplied data without encoding

If running an affected SharePoint Server version (2016, 2019, or below 16.0.19725.20384) with Project Server enabled and accessible to users, the environment is potentially affected by this XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 16.0.19725.20384 or later
Fixed in 16.0.19725.20384
Interim mitigation

Apply Microsoft's security patches for this vulnerability when available. In the interim, implement output encoding and input validation on user-supplied data, and consider restricting user permissions to minimize the attack surface.

Recommended fix Moderate confidence

SharePoint Server 2016/2019 with version 16.0.19725.20384 or later

  1. 1. Identify current SharePoint Server version via Central Administration > System Settings > Manage servers in farm
  2. 2. Review Microsoft SharePoint updates and ensure you obtain version 16.0.19725.20384 or later
  3. 3. Create a full backup of the SharePoint farm including content databases and configuration
  4. 4. Test the update in a non-production environment before applying to production
  5. 5. Apply the SharePoint Server update using the appropriate method (installer, patch, or cumulative update)
  6. 6. Run the SharePoint Products Configuration Wizard (PSConfig) after the update
  7. 7. Verify the farm is functioning correctly and the version shows 16.0.19725.20384 or later
  8. 8. Test critical SharePoint workflows and customizations to ensure compatibility
Caveat SharePoint updates may require re-application of customizations; test thoroughly in non-production environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45483 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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