403 forbidden

Author
Discussion

NiceCupOfTea

25,289 posts

251 months

Thursday 27th April 2023
quotequote all
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?

dhutch

14,388 posts

197 months

Thursday 27th April 2023
quotequote all
NiceCupOfTea said:
Just.... rolleyes

What is it, amateur hour!?
Mmmm

I'm sure it's not a 2min fix, but you would have thought it would be sorted by now eh!

98elise

26,608 posts

161 months

Friday 28th April 2023
quotequote all
NiceCupOfTea said:
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?
Its likely to be delete + something else used in SQL in the same line.

Edited to add, this post was fine, so "delete" on it's own doesn't trigger it



Edited by 98elise on Friday 28th April 09:40

jammy-git

29,778 posts

212 months

Friday 28th April 2023
quotequote all
98elise said:
NiceCupOfTea said:
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?
Its likely to be delete + something else used in SQL in the same line.

Edited to add, this post was fine, so "delete" on it's own doesn't trigger it



Edited by 98elise on Friday 28th April 09:40
The stupid thing is, NO other site I use has this issue. Just properly escape the text input and then you don't need to worry about SQL injection. It's like lesson 1 in secure web development!!

98elise

26,608 posts

161 months

Friday 28th April 2023
quotequote all
jammy-git said:
98elise said:
NiceCupOfTea said:
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?
Its likely to be delete + something else used in SQL in the same line.

Edited to add, this post was fine, so "delete" on it's own doesn't trigger it



Edited by 98elise on Friday 28th April 09:40
The stupid thing is, NO other site I use has this issue. Just properly escape the text input and then you don't need to worry about SQL injection. It's like lesson 1 in secure web development!!
Agreed, but it explains why it's happening even if it shouldn't be happening.

NiceCupOfTea

25,289 posts

251 months

Friday 28th April 2023
quotequote all
98elise said:
NiceCupOfTea said:
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?
Its likely to be delete + something else used in SQL in the same line.

Edited to add, this post was fine, so "delete" on it's own doesn't trigger it



Edited by 98elise on Friday 28th April 09:40
Yes, I got rid of all quotes and brackets, and looked for s(e)lect....from - whilst that wasn't there I noticed there was d(e)lete....from and surmised (not knowing anything about SQL) that that might also trigger it. Hey presto!

[and obviously I got a 403 forbidden when I posted this so had to had some brackets!)

98elise

26,608 posts

161 months

Saturday 29th April 2023
quotequote all
NiceCupOfTea said:
98elise said:
NiceCupOfTea said:
Just had this error posting a new thread.

After reading this thread and a bit of guesswork I realised it didn't like the word "delete" so I had to post it as "dlete" instead rolleyes

What is it, amateur hour!?
Its likely to be delete + something else used in SQL in the same line.

Edited to add, this post was fine, so "delete" on it's own doesn't trigger it



Edited by 98elise on Friday 28th April 09:40
Yes, I got rid of all quotes and brackets, and looked for s(e)lect....from - whilst that wasn't there I noticed there was d(e)lete....from and surmised (not knowing anything about SQL) that that might also trigger it. Hey presto!

[and obviously I got a 403 forbidden when I posted this so had to had some brackets!)
SQL is used to filter and manipulate data so words like...

Select
Insert
Update
Delete
Truncate
Add
Create
Etc

...are all valid SQL commands.



TonyRPH

12,973 posts

168 months

Saturday 29th April 2023
quotequote all
I suspect that some serious exploits have been found in the forum code, and this is their solution to circumvent any exploits.

I recall some years ago (must be about 12 years ago!) that some astute PHer(s) found some pretty bad exploits and reported it back then.

Maybe those have long since been fixed and maybe others have been found....

dhutch

14,388 posts

197 months

Saturday 29th April 2023
quotequote all
I'm sure the forum code is well behind what it now should be, behind the scenes as well as in terms of user interface.

I guess the issue is, how much time and money do you invest in that that? For what return? Especially due to the integration with articles on the wider site which mean an off the shelf solution wouldn't be instantly plug and play.

Equally, what is a website without a website, and the forum is a large part of what draws people in and keeps them here.

Condi

17,195 posts

171 months

Sunday 21st May 2023
quotequote all
I see there are 2 or 3 new threads about this problem....

Any closer to a fix, PH devs?

deadtom

2,557 posts

165 months

Thursday 25th May 2023
quotequote all
I've just started getting 403 errors when trying to reply to the Cardiff crash thread (https://www.pistonheads.com/gassing/topic.asp?h=0&f=205&t=2036191&i=0). It happens both when posting new reply and when trying to quote someone.


Fonzey

2,060 posts

127 months

Monday 24th July 2023
quotequote all
Heh. Just ran into this myself trying to update a post with the word "Delete"

Countdown

39,899 posts

196 months

Monday 24th July 2023
quotequote all
me too

r3g

3,148 posts

24 months

Friday 4th August 2023
quotequote all
98elise said:
SQL is used to filter and manipulate data so words like...

Select
Insert
Update
Delete
Truncate
Add
Create
Etc

...are all valid SQL commands.
This is quite interesting. I have just fallen foul of this myself with this reply :

"180??!!yikes

OFF WITH HIS HEAD!smash

<insertdefault "you should have set off earlier" comment here>

<insert detault whataboutery "what if a small child ran out into the road" comment here>"

I get 403 if I put the proper space between 'insert' and 'default'. It will only post if I remove the space so it's no longer 'insert' on its own. However it works ok with the other sentence. confused

768

13,682 posts

96 months

Friday 4th August 2023
quotequote all
I'm getting 500s everywhere now. Can't get to website feedback to post a new thread.

thegreenhell

15,354 posts

219 months

Friday 4th August 2023
quotequote all
Same here - 500 error in every sub forum. I can only get to individual threads through My Stuff.

Countdown

39,899 posts

196 months

Friday 4th August 2023
quotequote all
MeToo

Monkeylegend

26,401 posts

231 months

Friday 4th August 2023
quotequote all
Glad it's not just me then,

I can only get into threads that are already in My Stuff, everything else is an oops 403 forbidden.

Condi

17,195 posts

171 months

Friday 4th August 2023
quotequote all
Business as usual then


But have you noticed the new PH logo at the top of the page? biggrin

WyrleyD

1,903 posts

148 months

Friday 15th September 2023
quotequote all
Just happened to me too. Tracked it down to the word "SELECT" in mid sentence so changed it to "CHOOSE" and it went in OK. I know that "SELECT" is a SQL instruction so guess that's why it objected to it.