Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7703435
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T23:27:30+00:00 2026-05-31T23:27:30+00:00

I have a SQL Server 2005 database hosted on a shared hosting environment. Unfortunately

  • 0

I have a SQL Server 2005 database hosted on a shared hosting environment. Unfortunately for the last couple of months I have been having trouble with my application with some malicious scripts and html tags appended to the existing text in my database.

The text being injected is almost look like

"script src=http://somehostname/r.php ></script>"

I am using IIS 7 and enabled requestFiltering. But still the attack is hitting me so badly. How can I prevent my database from such attacks?

Thanks in advance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T23:27:31+00:00Added an answer on May 31, 2026 at 11:27 pm

    Any application that submits data into your table should strip this out as good practice. Of course, not all applications do.

    If your not using stored procedures, I suggest you create a trigger on the database table for INSERT and UPDATES and check if any illegal strings try and enter, if they do, reject the row. SQL has some string manipulation keywords such as CHARINDEX, I personally would check for common characters such as ‘\’, ‘;’, ‘$’, ‘&’ etc.

    I would also try and filter out anything that has already entered your tables and delete the rows:

    DELETE FROM Table
    WHERE Field LIKE '%<script>%'
    

    Alternatively, if you used a Stored Procedure and pass each field as a parameter then these characters would not enter your database.

    CREATE TRIGGER [dbo].[tr_CheckSQLInjection] 
    ON [dbo].[Notes]
    FOR INSERT, UPDATE
    AS
    
    BEGIN
    
    
    BEGIN TRANSACTION T_CHECKCHARACTERS
    
    BEGIN TRY
    
     -- YOUR LOGIC TO STRIP OUT THE CHARACTERS HERE
    
      COMMIT TRANSACTION T_CHECKCHARACTERS
    
    END TRY
    
    BEGIN CATCH
    
        RAISERROR('UNABLE TO COMMIT THE TRANSACTION', 1, 1)
    
        ROLLBACK TRANSACTION T_CHECKCHARACTERS
    
    END CATCH
    
    END
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a SQL Server 2005 database that has been deleted, and I need
I have a SQL Server 2005 database and I have 4 GB of text
I have a SQL Server 2005 database that is suffering from lock starvation because
We have a SQL Server 2005 database, and currently all our users are connecting
I have a SQL Server 2005 database that I'm trying to access as a
I have a SQL Server 2005 database that is linked to an Oracle database.
We have a Microsoft SQL Server 2005 database that needs to be converted back
We have a production SQL Server 2005 database server with the production version of
I have a 'reference' SQL Server 2005 database that is used as our global
I have an existing SQL Server 2005 database that runs our accounting/inventory application. We

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.