The news
CISA added CVE-2026-65660, a Microsoft SharePoint vulnerability involving code injection, to its Known Exploited Vulnerabilities catalog on September 25, alongside a MikroTik RouterOS issue (CVE-2026-67279). A day earlier it listed CVE-2026-5430, affecting several WSO2 API products, and CVE-2026-71362, an incorrect-authorization flaw in Adobe Commerce and Magento. Federal agencies were given until September 27 and 28 to remediate.
The SharePoint bug was fixed in Microsoft’s August 11 updates for SharePoint Server 2016, 2019 and Subscription Edition. Microsoft originally described it as a spoofing issue with a CVSS score of 6.5, but The Hacker News reported that the National Vulnerability Database scores it 8.8 and that Microsoft’s CVE record now calls it remote code execution. It requires a low-privileged authenticated user, but Viettel Cyber Security researcher Dinh Ho Anh Khoa says it can be chained with a separate authentication bypass, patched June 9, on servers that allow anonymous page access. According to SecurityWeek, threat intelligence platform Previdian said the exploitation attempts it saw on September 24 and 25 appeared to be based on Viettel Security’s technical write-up, and Microsoft said it had reliable evidence of attacks as of September 25.
For Adobe Commerce, The Hacker News reported a CVSS score of 9.1 and said e-commerce security firm Sansec had blocked exploitation attempts in August; the flaw can let attackers switch a shopper’s session to another customer’s account. For WSO2, the outlet reported a 9.8 score and said watchTowr captured in-the-wild attempts, including forged JWT tokens, in its honeypots on September 13. Affected WSO2 products include API Manager 4.1.0 through 4.6.0.
The numbers
- SharePoint CVSS (NVD)
- 8.8
- Adobe Commerce CVSS
- 9.1
- WSO2 CVSS
- 9.8
- SharePoint patch released
- Aug 11, 2026
Why CEOs should care
These are mainstream business platforms: document collaboration, online storefronts and API gateways. Ask IT to confirm that on-premises SharePoint servers carry the August updates (and the earlier June fix that blocks the anonymous-access chain), that any Adobe Commerce or Magento stores — including those run by agencies — are on the latest release, and that WSO2 gateways are patched.
The SharePoint case is a lesson in triage. A vulnerability labelled “moderate spoofing” turned out to allow code execution, so teams that prioritised strictly by vendor severity may have deferred it. Ask how your patch process handles rating changes and public exploit releases.
What’s next
With exploit details public, expect wider scanning. SharePoint 2013, which one researcher says is also affected, is out of support and will not be fixed.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error









