S-126: Members Area System 'view_func.php' Vulnerability


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-126: Members Area System 'view_func.php' Vulnerability
# 1  
Old 01-22-2008
S-126: Members Area System 'view_func.php' Vulnerability

Members Area System is prone to a remote file-include vulnerability because it fails to properly sanitize user-supplied input. The risk is MEDIUM. An attacker can exploit this issue to include an arbitrary remote file containing malicious PHP code and execute it in the context of the webserver process. This may facilitate a compromise of the application and the underlying system; other attacks are also possible.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Cybersecurity

Web Hack Attempt from whois 209.126.68.6

Anyone care to take a stab at decoding this hack attempt on a web server. From the error logs: $ cat error.log (36)File name too long: AH00036: access to... (4 Replies)
Discussion started by: Neo
4 Replies

2. Shell Programming and Scripting

SFTP return Error Code 126

Hi, We are getting the following error code while connection remote server using sftp command. sftp user@serrver Warning: child process (/opt/ssh2/bin/ssh2) exited with code 126. pls Advise. (2 Replies)
Discussion started by: koti_rama
2 Replies

3. UNIX for Advanced & Expert Users

Exit Status 126 - how to get rid of it

Hi All, I have a small application hosted on apache-tomcat 5. Basically its a html page which in turn calls a perl script residing on unix server. Through this perl script i am calling a shell script using system command , like system('scriptname.sh',arg1,arg2,arg3); Now in the script... (5 Replies)
Discussion started by: glamo_2312
5 Replies

4. AIX

ar: 0707-126

Trying to build code on IBM_AIX 5.3. Following error occured during build. ar: 0707-126 $projdir/obj/ibm/5.3/NewApp/NewApp.o is not valid with the current object file mode. Use the -X option to specify the desired object mode. ANy help is appreciated to resolve the error. (2 Replies)
Discussion started by: milindb
2 Replies
Login or Register to Ask a Question
wxBufferedDC(3erl)					     Erlang Module Definition						wxBufferedDC(3erl)

NAME
wxBufferedDC - See external documentation: wxBufferedDC. DESCRIPTION
See external documentation: wxBufferedDC . This class is derived (and can use functions) from: wxMemoryDC wxDC DATA TYPES
wxBufferedDC() : An object reference, The representation is internal and can be changed without notice. It can't be used for comparsion stored on disc or distributed for use on other nodes. EXPORTS
new() -> wxBufferedDC() See external documentation . new(Dc::wxDC() (see module wxDC)) -> wxBufferedDC() Equivalent to new(Dc, []) . new(Dc::wxDC() (see module wxDC), X::term()) -> wxBufferedDC() See external documentation . Alternatives: new(Dc::wxDC:wxDC(), Area::{W::integer(),H::integer()}) -> new(Dc,Area, []) new(Dc::wxDC:wxDC(), [Option]) -> wxBufferedDC() Option = {buffer, wxBitmap:wxBitmap()} | {style, integer()} new(Dc::wxDC() (see module wxDC), Area::{W::integer(), H::integer()}, Options::[Option]) -> wxBufferedDC() Types Option = {style, integer()} See external documentation . init(This::wxBufferedDC(), Dc::wxDC() (see module wxDC)) -> ok Equivalent to init(This, Dc, []) . init(This::wxBufferedDC(), Dc::wxDC() (see module wxDC), X::term()) -> ok See external documentation . Alternatives: init(This::wxBufferedDC(), Dc::wxDC:wxDC(), Area::{W::integer(),H::integer()}) -> init(This,Dc,Area, []) init(This::wxBufferedDC(), Dc::wxDC:wxDC(), [Option]) -> ok Option = {buffer, wxBitmap:wxBitmap()} | {style, integer()} init(This::wxBufferedDC(), Dc::wxDC() (see module wxDC), Area::{W::integer(), H::integer()}, Options::[Option]) -> ok Types Option = {style, integer()} See external documentation . destroy(This::wxBufferedDC()) -> ok Destroys this object, do not use object again AUTHORS
<> wxErlang 0.98.9 wxBufferedDC(3erl)