{"id":376,"date":"2026-11-19T07:47:40","date_gmt":"2026-11-19T06:47:40","guid":{"rendered":"https:\/\/mspbusiness.com\/en\/it-news\/patchwork-thursday-19-november\/"},"modified":"2026-11-19T07:49:28","modified_gmt":"2026-11-19T06:49:28","slug":"patchwork-thursday-19-november","status":"publish","type":"post","link":"https:\/\/mspbusiness.com\/en\/security\/patchwork-thursday-19-november\/","title":{"rendered":"Patchwork &#8211; Thursday 19 November"},"content":{"rendered":"<p id=\"top\"><strong>Today&#8217;s most serious item is a series of flaws in NGINX, two of which, in HTTP\/2, can lead to unauthenticated code execution and for which a public proof of concept is already circulating. In addition, CISA reports that an old flaw in Synology DSM is now being actively exploited, F5 is releasing only engineering hotfixes for six critical flaws in BIG-IP, WordPress 7.1.5 fixes twenty security issues and the official PyPI package for Microsoft Agent Framework distributed a credential stealer.<\/strong><\/p>\n<ul>\n<li><a href=\"#nginx\">Critical flaws in NGINX: unauthenticated code execution via HTTP\/2, proof of concept already public<\/a><\/li>\n<li><a href=\"#synology\">Old Synology DSM flaw now actively exploited: CISA adds it to the KEV list<\/a><\/li>\n<li><a href=\"#bigip\">Six critical flaws in F5 BIG-IP, only engineering hotfixes available<\/a><\/li>\n<li><a href=\"#wordpress\">WordPress 7.1.5 fixes twenty security issues, including a route to code execution<\/a><\/li>\n<li><a href=\"#agentframework\">Microsoft Agent Framework PyPI package hijacked to steal cloud keys<\/a><\/li>\n<\/ul>\n<h4 id=\"nginx\">Critical flaws in NGINX: unauthenticated code execution via HTTP\/2, proof of concept already public<\/h4>\n<table style=\"border-collapse: collapse; width: 100%; margin: 0.5em 0 1em;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Vulnerability<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Ten flaws in NGINX Open Source and NGINX Plus. The most serious are in HTTP\/2: an integer underflow in flow control (versions 1.9.5 up to and including 1.31.8) and a use-after-free in reverse proxying (versions 1.19.7 up to and including 1.31.8). There are also use-after-free flaws in HTTP\/3, the resolver and the mail proxy<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVE number<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">CVE-2026-123007 and CVE-2026-123633 (HTTP\/2), CVE-2026-121810 (HTTP\/3), CVE-2026-123634 (resolver), CVE-2026-113425 (mail proxy); others include CVE-2026-118899<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVSS score<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">9.2 (CVSS 4.0) for the five flaws that can lead to code execution; 8.7 for CVE-2026-118899<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Actively exploited<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No, no exploitation known as of 18 November. Rapid7 has, however, published a working proof of concept for CVE-2026-123007 on GitHub; the Dutch NCSC expects large-scale exploitation<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Patch available<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Yes, NGINX 1.30.7 (stable) and 1.31.9 (mainline), NGINX Plus 37.0.8.1 and 37.3.0.1. Temporary mitigation: disable HTTP\/2, which only covers the two HTTP\/2 flaws<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>How can the vulnerability be exploited?<\/strong><\/p>\n<p>According to <a href=\"https:\/\/www.wiz.io\/blog\/nginx-http2-rce-vulnerabilities\" target=\"_blank\" rel=\"noopener\">Wiz Research<\/a>, the flow control flaw only requires HTTP\/2 to be enabled. Wiz demonstrated code execution on a default configuration that simply serves static files, without a backend or additional modules, and ASLR does not stop the attack. The second HTTP\/2 flaw affects NGINX as a reverse proxy, particularly when free connections run out. Wiz, Ikotas Labs, Metnir, Rapid7 and Xint discovered the flaws independently of one another, partly with the help of AI. <a href=\"https:\/\/www.rapid7.com\/blog\/post\/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed\" target=\"_blank\" rel=\"noopener\">Rapid7<\/a> does add some caveats: its attack requires around 128 GB of HTTP\/2 traffic, relies on a specific memcpy path on processors with AVX-512 and is probably difficult to carry out behind a proxy.<\/p>\n<p><strong>What could the consequences be?<\/strong><\/p>\n<p>An attacker executes code with the privileges of the NGINX worker process. <a href=\"https:\/\/xint.io\/blog\/nginx2root-remote-code-execution\" target=\"_blank\" rel=\"noopener\">Xint<\/a> chained the flaw with a separate flaw in the Linux kernel to obtain root, in one test even from within a Docker container. According to Wiz, NGINX runs on more than 225 million websites and is also built into many appliances, container images and hosting panels. The <a href=\"https:\/\/www.ncsc.nl\/alerts\/kwetsbaarheden-in-f5-networks-nginx-update-nu\" target=\"_blank\" rel=\"noopener\">NCSC<\/a> rates both the likelihood and the potential damage as high.<\/p>\n<p><strong>What should IT administrators do now?<\/strong><\/p>\n<p>Take stock of where NGINX is running, including in containers and third-party products, and update to 1.30.7 or 1.31.9 or to your distribution&#8217;s patched package. A reload is not enough: restart NGINX fully or perform a binary upgrade so that the old workers disappear. If you cannot update yet, set <code>http2 off;<\/code> in the affected server blocks and remove the http2 parameter from the listen lines. Check the error log for crashing workers (\u2018exited on signal\u2019) and for long-running HTTP\/2 connections with many WINDOW_UPDATE frames. F5 has not yet announced a fix for NGINX Plus R34 to R36.<\/p>\n<p><a href=\"#top\">top ^<\/a><\/p>\n<h4 id=\"synology\">Old Synology DSM flaw now actively exploited: CISA adds it to the KEV list<\/h4>\n<table style=\"border-collapse: collapse; width: 100%; margin: 0.5em 0 1em;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Vulnerability<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Improper output encoding in the system plugin daemon of Synology DiskStation Manager (DSM) and BeeStation OS, allowing a remote, unauthenticated attacker to execute code. Affected are DSM 7.1 up to and including 7.2.2 in versions predating the November 2024 patches<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVE number<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">CVE-2024-10441<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVSS score<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">9.8<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Actively exploited<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Yes, added by CISA to the Known Exploited Vulnerabilities catalogue on 18 November 2026<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Patch available<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Yes, since November 2024: DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 and 7.1.1-42962-7 or later; BeeStation OS 1.1-65374 or later<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>How has this been exploited?<\/strong><\/p>\n<p>The flaw was demonstrated at Pwn2Own in 2024 and Synology fixed it in <a href=\"https:\/\/www.synology.com\/en-global\/security\/advisory\/Synology_SA_24_20\" target=\"_blank\" rel=\"noopener\">advisory Synology-SA-24:20<\/a>. Proof-of-concept code has been available online for some time. <a href=\"https:\/\/www.cisa.gov\/news-events\/alerts\/2026\/11\/18\/cisa-adds-four-known-exploited-vulnerabilities-catalog\" target=\"_blank\" rel=\"noopener\">CISA<\/a> now reports that the flaw is actually being exploited, without giving details about the attackers or the scale. US federal agencies must patch by 21 November, a remarkably short deadline.<\/p>\n<p><strong>What could the consequences be?<\/strong><\/p>\n<p>An attacker who can reach a NAS&#8217;s management interface gains full control of the device. For SME clients, a Synology often holds the file shares and the backups, making a compromised NAS a direct entry point for data theft and ransomware. In the same round, CISA also added flaws in LiteLLM, Apache Axis and REDCap to the list.<\/p>\n<p><strong>What should IT administrators do now?<\/strong><\/p>\n<p>Check the DSM version on all of your clients&#8217; Synology devices and update to one of the versions above or to the latest release. Pay particular attention to devices reachable from the internet via QuickConnect or forwarded ports, and to devices that have not been updated for years. Where possible, take the management interface off the internet and check suspicious devices for unknown accounts, tasks and packages.<\/p>\n<p><a href=\"#top\">top ^<\/a><\/p>\n<h4 id=\"bigip\">Six critical flaws in F5 BIG-IP, only engineering hotfixes available<\/h4>\n<table style=\"border-collapse: collapse; width: 100%; margin: 0.5em 0 1em;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Vulnerability<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Six stack-based buffer overflows in the data plane (TMM) of BIG-IP, BIG-IP Next for Kubernetes and BIG-IP CNF, which only occur in specific configurations with iRules or APM policies. There are also six less serious flaws, including in iControl SOAP and iControl REST<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVE number<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">CVE-2026-123637, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-120722; iControl SOAP: CVE-2026-125274<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVSS score<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">9.8 (CVSS 3.1) and 9.3 (CVSS 4.0) for the six critical flaws; 8.8 for the iControl SOAP flaw<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Actively exploited<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No, according to F5&#8217;s advisories of 18 November 2026<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Patch available<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Partially. For the six critical flaws, only engineering hotfixes via F5 Support (for BIG-IP Next for Kubernetes and CNF: 2.4.2-EHF1, 2.3.4-EHF1 and 2.2.5-EHF1); no workaround. The iControl SOAP flaw is fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>How can the vulnerability be exploited?<\/strong><\/p>\n<p>An unauthenticated attacker sends traffic to a virtual server on which a vulnerable configuration is active. According to <a href=\"https:\/\/thehackernews.com\/2026\/11\/f5-warns-6-critical-big-ip-flaws-can.html\" target=\"_blank\" rel=\"noopener\">The Hacker News<\/a>, this concerns iRules using MR::message, PSC::ip_address, GENERICMESSAGE::route, DNS::scrape or PEM::subscriber, and an APM per-request policy with the Client Information and Endpoint Security agents. Access to the management interface is not required. Four of the flaws were found by Sina Kheirkhah of watchTowr, the other two by F5 itself.<\/p>\n<p><strong>What could the consequences be?<\/strong><\/p>\n<p>The Traffic Management Microkernel crashes, halting all traffic through the BIG-IP until TMM has been restarted. F5 does not rule out code execution. Because BIG-IP often sits at the edge of the network, as a load balancer or for VPN access via APM, an outage directly affects the availability of client applications. An earlier F5 APM flaw was actively exploited after all following its disclosure in September.<\/p>\n<p><strong>What should IT administrators do now?<\/strong><\/p>\n<p>Review all iRules for the commands listed and check whether APM policies use the agents concerned. If so, request an engineering hotfix via F5 Support. F5 warns that these hotfixes do not go through the full testing process of regular releases, so test them first. For the iControl SOAP flaw, update to the fixed releases and until then restrict SOAP access to trusted networks. <a href=\"https:\/\/my.f5.com\/manage\/s\/article\/K000164058\" target=\"_blank\" rel=\"noopener\">F5&#8217;s overview<\/a> lists all advisories from this round.<\/p>\n<p><a href=\"#top\">top ^<\/a><\/p>\n<h4 id=\"wordpress\">WordPress 7.1.5 fixes twenty security issues, including a route to code execution<\/h4>\n<table style=\"border-collapse: collapse; width: 100%; margin: 0.5em 0 1em;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Vulnerability<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Twenty security fixes in WordPress core prior to 7.1.5, including unauthenticated privilege escalation via attributes of the Template Part block (which can lead to code execution), SQL injection in WP_Meta_Query, escalation to Super Admin on multisite, DoS via XML-RPC pingbacks and several stored XSS flaws<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVE number<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No CVE assigned in the release notes<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Actively exploited<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No, not reported (18 November 2026)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Patch available<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Yes, WordPress 7.1.5; fixes are being backported to all branches down to 4.7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>How can the vulnerability be exploited?<\/strong><\/p>\n<p>According to <a href=\"https:\/\/patchstack.com\/articles\/wordpress-7-1-5-security-release\/\" target=\"_blank\" rel=\"noopener\">Patchstack<\/a>, the most serious flaw starts with an attacker without an account who injects manipulated content via the attributes of the Template Part block. As soon as a user with the editor role opens that content, the attacker gains elevated privileges, with code execution as a possible consequence. The SQL injection in WP_Meta_Query can be exploited without authentication when a plugin or theme passes request data to meta_query. One stored XSS flaw in the Comment Date block requires only an account with the contributor role and executes for every visitor.<\/p>\n<p><strong>What could the consequences be?<\/strong><\/p>\n<p>A compromised WordPress site can serve malware or skimmers, leak customer data or act as a stepping stone into the hosting environment. According to the <a href=\"https:\/\/wordpress.org\/news\/2026\/11\/wordpress-7-1-5-release\/\" target=\"_blank\" rel=\"noopener\">release notes<\/a>, five fixes are contained in an update to the Gutenberg package, so they do not stand out in the regular list of changed PHP files.<\/p>\n<p><strong>What should IT administrators do now?<\/strong><\/p>\n<p>For managed client websites, check whether automatic background updates are actually working and whether 7.1.5 has been installed; otherwise update via the dashboard or your management tool. Sites on an older branch will receive the backported fixes as soon as they are ready. Patchstack also recommends checking who has the contributor role or higher and, on multisite installations, reviewing the list of administrators.<\/p>\n<p><a href=\"#top\">top ^<\/a><\/p>\n<h4 id=\"agentframework\">Microsoft Agent Framework PyPI package hijacked to steal cloud keys<\/h4>\n<table style=\"border-collapse: collapse; width: 100%; margin: 0.5em 0 1em;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Vulnerability<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Supply chain attack on Microsoft&#8217;s official Python package agent-framework on PyPI. The malicious versions 1.26.1 and 1.26.2 contain a credential stealer that runs every time Python starts. Version 1.26.0 is safe<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">CVE number<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No CVE assigned<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Actively exploited<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">Yes, both versions were published on 17 November 2026 and subsequently quarantined by PyPI<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #999; padding: 6px 10px; font-weight: 600; vertical-align: top; width: 160px;\">Patch available<\/td>\n<td style=\"border: 1px solid #999; padding: 6px 10px; vertical-align: top;\">No, this is not a software flaw. Roll back to version 1.26.0, rebuild environments and rotate all reachable credentials<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>How has this been exploited?<\/strong><\/p>\n<p>An unknown party obtained publishing access to the package, which is downloaded around 200,000 times a month. According to <a href=\"https:\/\/www.bleepingcomputer.com\/news\/security\/microsofts-agent-framework-pypi-package-compromised-to-steal-credentials\/\" target=\"_blank\" rel=\"noopener\">BleepingComputer<\/a>, the attacker planted a .pth file that loads the stealer every time Python starts, even if the package itself is never imported. The framework continued to work normally. After PyPI quarantined version 1.26.1, version 1.26.2 appeared roughly two and a half minutes later, suggesting that the attacker still had access at that point. Socket, StepSecurity, Ox Security and <a href=\"https:\/\/www.wiz.io\/blog\/malicious-version-of-microsofts-agent-framework-published-to-pypi\" target=\"_blank\" rel=\"noopener\">Wiz<\/a> mapped out the attack. How the attacker gained access is still unknown.<\/p>\n<p><strong>What could the consequences be?<\/strong><\/p>\n<p>The stealer searches environment variables, configuration files and processes for keys for Azure, AWS, GitHub, Docker, Hugging Face and OpenAI. It also attempts to retrieve Azure managed identity tokens and Azure DevOps OIDC tokens; version 1.26.2 additionally targets GitHub Actions OIDC tokens and runner directories. Everything is sent to an endpoint on webhook.site. A successful installation in a build pipeline can thus give access to clients&#8217; entire cloud environments.<\/p>\n<p><strong>What should IT administrators do now?<\/strong><\/p>\n<p>Search development environments, container images and CI\/CD pipelines for agent-framework 1.26.1 or 1.26.2 and for the files agent_framework_meta.pth and af_runtime_diag.pth. Isolate affected systems, rebuild them from a clean base with version 1.26.0 and rotate all credentials that were reachable from that environment. Check egress logs for traffic to webhook.site and pin package versions in your pipelines so that a new version cannot be pulled in unnoticed.<\/p>\n<p><a href=\"#top\">top ^<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>NGINX hit by critical HTTP\/2 flaws with public proof of concept. Plus Synology DSM actively exploited, F5 BIG-IP flaws, WordPress 7.1.5 and hijacked Microsoft PyPI package.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"mspb_bron_id":1169723,"mspb_url_nl":"https:\/\/mspbusiness.com\/security-en-privacy\/patchwork-donderdag-19-november\/","mspb_url_de":"https:\/\/mspbusiness.com\/de\/security\/patchwork-donnerstag-19-november\/","mspb_url_en":"","mspb_beeld_url":"https:\/\/mspbusiness.com\/wp-content\/uploads\/2026\/09\/patchwork-P.png","mspb_beeld_klein":"https:\/\/mspbusiness.com\/wp-content\/uploads\/2026\/09\/patchwork-P-400x225.png","mspb_auteur":"Redactie","mspb_beeld_alt":"","mspb_video":"","_yoast_wpseo_metadesc":"NGINX fixes critical HTTP\/2 flaws with public proof of concept; Synology DSM actively exploited, F5 BIG-IP hotfixes, WordPress 7.1.5 and a PyPI attack.","footnotes":""},"categories":[3],"tags":[],"layout":[6],"class_list":["post-376","post","type-post","status-publish","format-standard","hentry","category-security","layout-news"],"_links":{"self":[{"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/posts\/376","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/comments?post=376"}],"version-history":[{"count":1,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/posts\/376\/revisions"}],"predecessor-version":[{"id":377,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/posts\/376\/revisions\/377"}],"wp:attachment":[{"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/media?parent=376"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/categories?post=376"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/tags?post=376"},{"taxonomy":"layout","embeddable":true,"href":"https:\/\/mspbusiness.com\/en\/wp-json\/wp\/v2\/layout?post=376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}