PHP Fatal error: require(): Failed opening required...tpl_images5f8e_1jpg_default.php

I get these errors, this is one example, but the file it is looking for it doesn't exist. Its an image reference wrapped in a tpl mention, each error log is different mentioning a different image name somehwo:--

PHP Warning: require(includes/templates/template_default/templates/tpl_images5f8e_1jpg_default.php): failed to open stream: No such file or directory in /chroot/*******/common/tpl_main_page.php on line 244.

HeathenMagic:

I get these errors, this is one example, but the file it is looking for it doesn't exist. Its an image reference wrapped in a tpl mention, each error log is different mentioning a different image name somehwo:--
Not so good to have that scenario I think. Basically at it would seem that if the correct data is fed for selecting an image, then whatever file is named by that "image" could be retrieved/accessed by being required into the page load. Would look to see what if any changes have been made to the site's software as this may be something that has been introduced or perhaps the template allows this as compared to a default install...

tpl_images5f8e_1jpg_default
Could it be related to a url-rewriter that's got wrong rules set up?

No such file or directory in /chroot/******...
The chroot part does suggest that someone's attempting something malicious.

mc12345678:

Not so good to have that scenario I think. Basically at it would seem that if the correct data is fed for selecting an image, then whatever file is named by that "image" could be retrieved/accessed by being required into the page load. Would look to see what if any changes have been made to the site's software as this may be something that has been introduced or perhaps the template allows this as compared to a default install...

Thanks for your reply. I do recall having this for the previous template, but was stumped also. I carefully merged for 1.57 upgrade, albeit there are quire a few modules so this gives me a starting point to see if its one of them.

Ah that might be a possibility, I have 'ultimate seo urls' installed, and I believe this had to have .htaccess altered. I also have two domains that point to the main domain (so I have a .co.uk and .uk pointing to .com) so not sure if that is a possibility. But think maybe the ultimate urls module is likely the culprit.