24/5 Hotline Support Service

+44 (0)20 3588 3841

Open a Support Ticket

Configuring the User Interface for Custom Send To Actions in Netsparker Standard

Netsparker Standard has an ability to create issues in common issue tracking system. [Link may be added for the list of send to actions] Netsparker also enables users to create custom send to actions.

As an example, the article will implement a basic Send To action that sends a found vulnerability in an email message. There are three steps to this process:

  1. Step 1: The Skeletal Implementation of the Interface
  2. Step 2: Creating the Interface
  3. Step 3: The Code to Send the Email

This topic explains how to create and configure a Send To action in Netsparker Standard.

Step 1: The Skeletal Implementation of the Interface

Send To actions use the default extensibility mechanism provided with Netsparker Standard and can be developed in either C# or VB.NET. You may use any other .NET language if you can compile the code to an assembly. In this example, we use C#.

To create a Send To action you need to implement a simple interface called ISendToAction. Create an extensions.cs file in your Documents\Netsparker\Scripts folder and paste this code into it. If you already have an extensions.cs file, you may append this new class, the basic skeletal implementation of the interface:

using System;
using System.Drawing;
using DevExpress.Utils.Svg;
using MSL.Core.Entities.Vulnerability;
using MSL.Core.Process.SendTo;

public class MailSendToAction : ISendToAction
        public string DisplayName
                get { return "Mail"; }

        public Bitmap SmallIcon
                get { return null; }

        public Bitmap LargeIcon
                get { return null; }

        public SvgImage SvgImage
                get { return null; }

        public SettingsObjectBase CreateSettingsObject()
                throw new NotImplementedException();

        public string Execute(IVulnerabilityView vulnerability, SettingsObjectBase settings)
                throw new NotImplementedException();

This table is an explanation of all the elements in the interface:

UI Element



This is a property where you should return a string that denotes the name of your action.


These properties should return an icon representing your action in sizes 16*16/32*32 respectively. You may return null from these properties.


This method should return an instance of SettingsObjectBase class (or a derived one) where the action settings are listed as properties.


This is the method where the action will be performed. In this case, we format the vulnerability instance and send it as an email with the specified settings.

Step 2: Creating the Settings Interface

Next, create the Settings class by extending the SettingsObjectBase class. Paste the following code after the code in Step 1, before the last closing brace:

public class Settings : SettingsObjectBase
        private const int DefaultPort = 25;

        private const SmtpDeliveryMethod DefaultDeliveryMethod = SmtpDeliveryMethod.Network;

        private const string DefaultBodyTemplate = "Mail.cshtml";

        public Settings()
                Port = DefaultPort;
                DeliveryMethod = DefaultDeliveryMethod;
                BodyTemplate = DefaultBodyTemplate;

        [Description("The server name or IP address to send mail from.")]
        public string Host { get; set; }

        [Description("The port number to be used.")]
        public int Port { get; set; }

        [Description("The name of the user to be used for authentication.")]
        public string Username { get; set; }

        [Description("The password of the user to be used for authentication.")]
        public string Password { get; set; }

        [DisplayName("From Address")]
        [Description("The address that mail will be send from.")]
        public string FromAddress { get; set; }

        [DisplayName("To Address")]
        [Description("The address that mail will be send to.")]
        public string ToAddress { get; set; }

        [DisplayName("Enable SSL")]
        [Description("Specify whether SSL will be used.")]
        public bool EnableSsl { get; set; }

        [DisplayName("Delivery Method")]
        [Description("Specify how outgoing email messages will be handled.")]
        public SmtpDeliveryMethod DeliveryMethod { get; set; }

        [DisplayName("Body Template")]
        [Description("The template file to be used while rendering mail contents.")]
        public string BodyTemplate { get; set; }

You will also need to add these three new directives:

using System.ComponentModel;
using System.Net;
using System.Net.Mail;

Now that we have a settings class, we can return an instance of it from our CreateSettingsObject() method as explained below:

public SettingsObjectBase CreateSettingsObject()
        return new Settings();

The Settings class does not have any action and does not execute anything. It only outlines the required configuration details as .NET properties. This class will be rendered in the Netsparker Standard Settings UI, as illustrated, and must be configured by the user.

This table lists and explains the properties along with several attributes.




This property specifies which category it belongs to. You are free to create your own.


This is the help text that will be shown in the UI when this property is selected.


By default, the name of the property is shown in the UI. You can override it using this attribute.


This attribute indicates that the property contains sensitive data and should be masked in the user interface.


This specifies the default value of the property. Ensure that you initialize this value on the constructor of your Settings class. With this attribute in place, users can right click and reset this setting to its default value.

Step 3: The Code to Send the Email

The final piece of code is the actual implementation that sends the vulnerability details in an email. Update your Execute() method with the following code:

public string Execute(IVulnerabilityView vulnerability, SettingsObjectBase settings)
        var settingsTyped = (Settings)settings;

        var smtp = new SmtpClient
                Host = settingsTyped.Host,
                Port = settingsTyped.Port,
                EnableSsl = settingsTyped.EnableSsl,
                DeliveryMethod = settingsTyped.DeliveryMethod,
                Credentials = new System.Net.NetworkCredential(settingsTyped.Username, settingsTyped.Password),

        string contents;

                contents = vulnerability.RenderSendToTemplate(settingsTyped.BodyTemplate);
        catch (Exception e)
                throw new Exception(string.Format("An error occurred while rendering template '{0}', make sure it exists.", settingsTyped.BodyTemplate), e);

        using (smtp)
        using (var message = new MailMessage(settingsTyped.FromAddress, settingsTyped.ToAddress))
                message.Subject = string.Format(settingsTyped.TitleFormat, vulnerability.Title);
                message.Body = contents;

        return "Vulnerability sent as mail successfully!";

This is simple .NET code that configures a SmtpClient instance and sends an email message with the settings provided. One point to note is that as the Body of the email message, we are rendering the vulnerability details with a template. For this example we are using a template called Mail.cshtml as the default template.

For such an example to work, you must create a file called Mail.cshtml in your Documents\Netsparker\Resources\Send To Templates folder with the following code:

@using MSL.Core;
@using MSL.Core.Entities.Vulnerability;
@using MSL.Common.Text.Encoding;
        // Short access to some object
        var vuln = Model.Vulnerability;
        var absoluteUri = Model.Vulnerability.Response.ResponseUri.AbsoluteUri;
        var attackParameter = Model.Vulnerability.Response.UriManager.AttackParameter;
}URL: @Raw(Decode.Url(absoluteUri))
Certainty: @vuln.Certainty%
Confirmed: @vuln.IsConfirmed
Parameter Name: @attackParameter.Name
Parameter Type: @attackParameter.Type
Attack Pattern: @Decode.Url(attackParameter.Value)
@foreach (var customFieldPair in vuln.CustomFields)
 @customFieldPair.Key<text> :</text> if (customFieldPair.Value.HasMultipleValues)
        foreach (var value in customFieldPair.Value.Values)

You can modify this template or create other templates based on it. You can also select the template to use in the Settings pane of your Send To action. Here is a sample email that is sent using this template.


Testing the Send To Action

By default, you cannot test the Send To Action while you are configuring it in the Settings UI. To enable this, you need to implement ISendToActionTestable rather than ISendToAction.

Since this interface has an extra method called Test(), it should be implemented too. By using this method, you simply need to test whether the provided settings are valid and return a SendToActionTestResult with success or failure information.


This is how you implement a basic Send To action. Even though it requires some adapting and error checking, you can use this code to send the details of the vulnerabilities discovered by Netsparker web application security scanner as emails. You can also download the full source code of this example from here:

For information on how to configure auto send to actions, see Configuring Auto Send To Actions in Netsparker Standard.


Dead accurate, fast & easy-to-use Web Application Security Scanner