#SPFx Accordion Webpart Example enjoysharepoint.com/spfx-acc…

I'm already blowing up demand from within. There's a SharePoint webpart that can serve web apps, so I am building a pipeline to make arbitrary dashboards through windsurf. There's basically no reason to use SaaS like Tableau anymore.

Continuing the journey into the power of MCP Server MCP-UI 🚀 Now across 3 scenarios: Claude Chat, Vite App, and SPFx WebPart—same tool, different contexts. Powered by mcpui.dev/ (server client) Next step? Microsoft Copilot 🙂 #MCP #SPFx #M365Dev #PnP

I am about 15 hours into using Claude Code on a Max subscription using Opus 4.5 with a fairly small size existing code base. My main purpose in this is to evaluate the tool and I’m so far not impressed either. The good parts: 1. Claude Code scanned the code base and generated a pretty good Claude(dot)md file which acts as king of a fact table for the app. ex: logic goes here, data access goes there, etc. You can then tweak it however you like but it did a good job with this. 2. Using a CLI tool outside your IDE opens up the scope of files the LLM will consider for a request significantly. This enables it to follow established patterns more accurately. 3. After making the updates, Claude Code will compile the app and automatically attempt to correct any errors and will keep going until it hits zero errors. 4. Using Claude Code CLI appears to be heavily subsidized with unbelievably generous token allocations at a much cheaper price. 5. You can write prompts with a level of detail you’d give to a junior developer and get a fairly close initial design that can have several features. The bad parts: 1. It makes mistakes. It will invent parameters or use parameters that are inappropriate for the parent parameter. 2. It’s not even close to a final system. It doesn’t automatically put in error checking and recovery. It will design things that will work in a test environment but not in prod. It effectively does UI prototypes and I have been wholly unable to get it to move beyond what I would consider a prototype. Too many categories to list. 3. Want to harp on the prototype aspect. A good analogy is Sharepoint development I did in the 00s. Sharepoint is a system that lets you get a working app up and running with a lot of features very quickly. Then the user will ask you to move something from the right side of the screen to the left side. And you’re forced to tell them, “That’ll take two weeks of work” because you need to create a custom WebPart to do that. And they’re flabbergasted. But AI coding is similar - if you have little idea on how your app should operate then you’ll likely be satisfied with what Claude Code comes up with. If you are in the slightest opinionated with a clear vision on what you want, you’ll be very frustrated as Claude Code fails repeatedly to fulfill your vision and you end up doing it by hand.

GitHub - soltanali0/CVE-2025-53770-Exploit: SharePoint WebPart Injection Exploit Tool github.com/soltanali0/CVE-20…

یک رایتاپ عالی درمورد کاستوم webpart توی شیرپونیت که باهاش به یک اسیب پذیری جالب رسیده واقعا عالی بود 👑

Learn how to use the Microsoft 365 Copilot agent link webpart for SharePoint Online. linkedin.com/feed/update/urn…

The beauty of suave being so lightweight is that I can simply copy a built-in webpart, update in my code and just keep living I should contribute back the proxy that supports chunked responses though

CVE-2025-53770: SharePoint WebPart Injection Exploit Tool darkwebinformer.com/cve-2025…

SharePoint WebPart Injection Exploit Tool github.com/soltanali0/CVE-20…

Check out my latest article : CVE-2025-53770 : Deep-Dive on the SharePoint WebPart Injection RCE (“ToolPane / ToolShell”) via @LinkedIn linkedin.com/pulse/cve-2025-… #InfoSec #CyberSecurity

SharePoint WebPart Injection Exploit Tool github.com/soltanali0/CVE-20…

GitHub - soltanali0/CVE-2025-53770-Exploit: SharePoint WebPart Injection Exploit Tool github.com/soltanali0/CVE-20…

CVE-2025-49704: This vulnerability arises from the implementation of the SurrogateSelector interface. CVE-2025-49706 authentication bypass, allows import/update operations on SharePoint WebPart components via the ToolPane endpoint. Accordingly, you can contact the @hawktrace

Microsoft SharePointにおいて、WebPartプロパティのデシリアライズ処理に関連する新たなリモートコード実行（RCE）脆弱性が報告された。この脆弱性は、細工されたXMLペイロードをWebPartに埋め込むことで任意コードを実行でき、SharePoint環境全体が危険に晒される可能性があった。 特にwebpartpages.asmxエンドポイント経由でSPThemesクラスの不安全なデシリアライズが悪用可能であった。Microsoftは既に修正パッチを公開しているが、影響を受ける環境では速やかな更新とWebPart入力の厳格な検証が推奨される。 cybersecuritynews.com/sharep…

SharePoint Unknown CVE Unveiled: RCE via WebPart Properties Deserialization reddit.com/r/blueteamsec/com…

Bug on sp-list-webpart - flashing due to an error in the React setState, which started happening this morning. #M365 #MicrosoftBugs #Help

📢New #SharePoint FAQ WebPart: Powered by #Microsoft365 #Copilot ▶Generate quality FAQs directly from documents, meeting transcripts, or other content. ▶Refine, reorder and validate questions & answers before publishing. 🔗Check out more details: techcommunity.microsoft.com/…

Script editor web part in #SharePoint enable script editor webpart in sharepoint online enjoysharepoint.com/script-e…

Unlock SharePoint's Potential with the Call to Action Web Part I explore text editing, background image customization, and more. iwmentor.com #SharePoint #CallToAction #webpart #WebDesign #Tutorial #Microsoft365 #TechTips