Critical Vulnerability Fixed in the ISpring Gift Shop Module for 1C-Bitrix

A critical vulnerability was found in the third-party ISpring Gift Shop module for 1C-Bitrix. A fix is available in version 0.7.0; site owners using the module should check their installed version.

· 4 min read · 4 comments

On November 12, 2026, Habr reported a vulnerability in the third-party ISpring Gift Shop module for 1C-Bitrix: Site Manager. The issue affects version 0.6.0; the developer, iSpring, released a fix in version 0.7.0. Site owners using the module are advised to check their installed version and update it if necessary.

What We Know About the Vulnerability

The vulnerability is listed in the Russian Federal Service for Technical and Export Control’s vulnerability database under BDU:2026-08451. It is rated critical, with a CVSS 3.1 score of 9.8. The cause is missing authentication for a critical module function. According to the database entry, a remote attacker could cause a denial of service.

The entry also notes that an exploit exists. But it provides neither a CVE identifier nor evidence of confirmed exploitation in real-world incidents. The existence of an exploit should not be reported as evidence that sites have been affected: the source provides no such information. At the same time, there is no need to wait for incident reports before checking the installed version.

It is important not to overstate the scope of the problem. The vulnerability is not in the 1C-Bitrix: Site Manager core or its built-in components. It affects a specific third-party module, version 0.6.0. Sites without this module do not need the fix. Where the module is used, updating the platform itself will not replace updating the module: the fix was released separately.

How to Check the Module and Install the Fix

Start by checking whether ispring.sdosync is installed and identifying its actual version. Using 1C-Bitrix does not, by itself, mean that a particular site has ISpring Gift Shop installed. If version 0.6.0 is installed, the recommendation is to update the module to 0.7.0 or later through the official Marketplace.

After updating, confirm that the new version is installed and check the iSpring Learn integration and the gift shop’s main workflows. The recommendation is not just to run the update, but also to test the features for which the module was added to the site. If you cannot update or need help, the module’s Marketplace listing provides a support address: [email protected].

The source gives no specific deadline for installing the fix. The recommendation, however, is not to put off the check and, if the vulnerable version is found, to move to a fixed version as soon as possible. This applies specifically to sites with this module, not to every project on the platform.

What This Means for Site Owners and Teams

Site owners should give their teams a task with precise criteria: this is a third-party component, and its fix is not included in a platform update. The team’s response should make clear whether the published information applies to the site and whether the work is complete, including checks of the integration and gift shop workflows. “Bitrix is up to date” does not answer that question on its own.

For a marketer or store owner, the practical risk is a potential denial of service. This is not about page layouts or how easy it is to choose a product: according to the vulnerability database, the issue could allow a remote attacker to disrupt the service. The critical rating explains why it makes sense to prioritize this task over routine site changes, without suggesting that every 1C-Bitrix project is vulnerable.

It helps to distinguish between the platform’s scope and that of the components connected to it. As with vulnerabilities in a third-party WordPress plugin, the name of the CMS does not tell you whether the affected module is installed on a particular site. What matters is what this site actually uses, not a general assumption that the entire platform is safe or vulnerable.

My Take: “Everything Is Up to Date” Is Too Vague

I wouldn’t panic over the critical rating, but I wouldn’t accept “we updated the platform recently” as an answer, either. As a store owner, I need a clear account of what the team has done, not a reassuring status in a report. Especially when the component supports familiar workflows on the site: I’ve already seen attractive changes that left shoppers unable to find sizes.

An off-the-shelf platform for selling clothes still seems more practical to me than maintaining custom code. But the modules added to it need attention in their own right. If this task requires help, I’d ask for a clear scope of work and a figure I can budget for. “We’ll see as we go” is not very reassuring when the check is urgent.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. Уязвимость в стороннем модуле «Магазин подарков ISpring»: обновитесь до версии 0.7.0 habr.com

About the author

Eva P.

children’s clothing store owner

I run a small children’s clothing store and put together the product range on the website myself. I’ve already seen a beautiful redesign after which customers could no longer find the sizes.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. Does the advisory specify which module function lacks authentication, or whether upgrading to 0.7.0 requires any configuration changes? That would help teams verify the fix beyond checking the version number.

    1. Eva P. Post author

      The advisory details missing authentication for a critical module function, but doesn’t name that function or mention configuration changes for 0.7.0. I wouldn’t treat the version number alone as proof the buyer journey is safe; teams should confirm the module update completed and test checkout, rather than discover a broken gift flow after launch.

    2. For our learning center, I ask whoever maintains the site to record the module version and the date it was checked; “everything is up to date” is not enough to plan staff time or assess risk. If the advisory does not name the affected function or configuration changes, I’d treat 0.7.0 as the practical minimum and ask the maintainer to confirm the update on the live site.

    3. From the details here, the advisory only says authentication is missing for a critical module function; it doesn’t name the function or mention configuration changes for 0.7.0. If the release notes spell that out, that’d be useful—otherwise teams may need to verify the update with iSpring rather than treating the version number as the whole security check.