# Security Bulletins 2010-004 and 2010-005 published

**URL:** <https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400>\
**Category:** OXID Announcements\
**Tags:** security\
**Created:** [October 20, 2010, 3:13pm UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400 "2010-10-20T15:13:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marco.steinhaeuser](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/marco.steinhaeuser/32/1832_2.png) [@marco.steinhaeuser](https://forum.oxid-esales.com/u/marco.steinhaeuser)\
**Post date:** [October 20, 2010, 3:13pm UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400/1 "2010-10-20T15:13:22Z")

</div>

Hi everybody,

the following security bulletins have been published just now:  
[http://wiki.oxidforge.org/Security\_bulletins/2010-004](http://wiki.oxidforge.org/Security_bulletins/2010-004)  
[http://wiki.oxidforge.org/Security\_bulletins/2010-005](http://wiki.oxidforge.org/Security_bulletins/2010-005)

Both issues have been addressed in patch 4.4.3 of OXID eShop all editions. Partners, owners of support contracts and NDA owners have been informed when we published patch 4.4.3.

Regards

---

<div class="post-metadata">

**Author:** ![MBa](https://forum.oxid-esales.com/letter_avatar_proxy/v4/letter/m/4491bb/32.png) [@MBa](https://forum.oxid-esales.com/u/MBa)\
**Post date:** [October 26, 2010, 4:52pm UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400/2 "2010-10-26T16:52:52Z")

</div>

Hi,  
I have a question.

If you work with a very strong customized template, you don’t can support every template-change in shop updates.

So, is it possible, if there changes for security in the template, to publish them.

I now, its a security question and better don’t publish.  
But I think, these bug should be fixed in logic, not in templates. So if there is a security-fix inside templates, please publish.

---

<div class="post-metadata">

**Author:** ![marco.steinhaeuser](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/marco.steinhaeuser/32/1832_2.png) [@marco.steinhaeuser](https://forum.oxid-esales.com/u/marco.steinhaeuser)\
**Post date:** [October 28, 2010, 9:56am UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400/3 "2010-10-28T09:56:49Z")

</div>

Hello Markus,

of course: If there is a way to easily fix such issues via templates or really simple steps, we will publish.

> But I think, these bug should be fixed in logic, not in templates

It was done like this.

Regards

---

<div class="post-metadata">

**Author:** ![MBa](https://forum.oxid-esales.com/letter_avatar_proxy/v4/letter/m/4491bb/32.png) [@MBa](https://forum.oxid-esales.com/u/MBa)\
**Post date:** [October 28, 2010, 10:55am UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400/4 "2010-10-28T10:55:40Z")

</div>

Hi Marco,

thanks. If I look in the security bulletins, there is no case like this. So I was not shure.

---

<div class="post-metadata">

**Author:** ![system](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/system/32/4245_2.png) [@system](https://forum.oxid-esales.com/u/system)\
**Post date:** [July 13, 2026, 8:35pm UTC](https://forum.oxid-esales.com/t/security-bulletins-2010-004-and-2010-005-published/46400/5 "2026-07-13T20:35:37Z")

</div>

Closed on July 13, 2026, 8:35pm UTC