<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PHP on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/php/</link>
    <description>Recent content in PHP on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Aug 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/php/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A few notes on WordPress Security</title>
      <link>https://insinuator.net/2018/08/a-few-notes-on-wordpress-security/</link>
      <pubDate>Wed, 22 Aug 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/08/a-few-notes-on-wordpress-security/</guid>
      <description>&lt;p&gt;Taking a look at the &lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=wordpress&#34;&gt;CVE List for WordPress&lt;/a&gt;, most vulnerabilities aren’t found within the WordPress core but inside of third-party plugins and themes.&lt;/p&gt;&#xA;&lt;p&gt;Today, let’s talk about WordPress.&lt;/p&gt;&#xA;&lt;p&gt;Performing a WordPress assessment might seem boring at first as core functionality [tested] and configuration does not allow for extensive security misconfigurations. Luckily, most instances use plugins and themes to add features not offered by the WordPress core.&lt;/p&gt;&#xA;&lt;p&gt;In this blog post I would like to discuss the findings and how I discovered them. Also, I will describe different vendor responsiveness reaching from not responding at all, to not understanding the issue to fast and professional responses kindly asking for a review of the updated code ready for deployment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
