Recent Topics
  1. b2evolution CMS Support Forums
  2. b2evolution Development
  3. Bug reports
  4. Bugs in 5.x
  5. comment_post.php cross-site scripting

comment_post.php cross-site scripting

1 Jan 08, 2015 01:17    

Whilst looking for an answer to another problem I came across this article. Does anyone know the truth of this. The article notes there was no resolution to this in Sept 2104 since 2011

http://xforce.iss.net/xforce/xfdb/66118

b2evolution comment_post.php cross-site scripting

Description:

b2evolution is vulnerable to cross-site scripting, caused by improper validation of user-supplied input by the comment_post.php script. A remote attacker could exploit this vulnerability using the p parameter to inject malicious script into a Web page which would be executed in a victim's Web browser within the security context of the hosting Web site, once the page is viewed. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.

*CVSS:
Base Score: 4.3
Access Vector: Network
Access Complexity: Medium
Authentication: None
Confidentiality Impact: None
Integrity Impact: Partial
Availability Impact: None

Temporal Score: 4.1
Exploitability: High
Remediation Level: Unavailable
Report Confidence: Uncorroborated

Consequences:

Gain Access

Remedy:

No remedy available as of September 1, 2014.

References:

AutoSec Tools Web Site: b2evolution 4.0.3 Persistent Cross-site Scripting.
b2evolution Web site: b2evolution.
BID-46886: b2evolution Comment HTML Injection Vulnerability
OSVDB ID: 71192: b2evolution blogs/htsrv/comment_post.php p Parameter XSS
SA43725: b2evolution p Script Insertion Vulnerability

Platforms Affected:

b2evolution b2evolution 4.0.3

Reported:

Mar 15, 2011

Back to top

2 20 Jan 2015 07:19

Hi @amoun,

Although the "p" parameter mentioned in the report doesn't exist anymore ( since version 4.1.5 ), the dev team have checked again and did not find anything dangerous, or at least, that particular issue is already solved.

We think that the security settings stablished by default for each group ( http://b2evolution.net/man/blogging-permissions ) are enough for a wide range of situations. So, users are encouraged to do not change them unless they actually know what are they doing and the implied risks of those changes.

Regards!

Back to top


Form is loading...