Server-Side Request Forgery (SSRF) vulnerability in Rank Math SEO plugin <= 1.0.95 at WordPress.

**Rank Math SEO plugin vulnerable to Server-Side Request Forgery**

Critical severity GitHub Reviewed Published Sep 10, 2022 • Updated Sep 16, 2022

GHSA-j95r-86hx-xwxg: Rank Math SEO plugin vulnerable to Server-Side Request Forgery

The critical flaw in BackupBuddy is one of thousands of security issues reported in recent years in products that WordPress sites use to extend functionality.

Attackers are actively exploiting a critical vulnerability in BackupBuddy, a WordPress plug-in that an estimated 140,000 websites are using to back up their installations.

The vulnerability allows attackers to read and download arbitrary files from affected websites, including those containing configuration information and sensitive data such as passwords that can be used for further compromise.

WordPress security vendor Wordfence reported observing attacks targeting the flaw beginning Aug. 26, and said it has blocked close to 5 million attacks since then. The plug-in's developer, iThemes, issued a patch for the flaw on Sept. 2, more than one week after the attacks began. That raises the possibility that at least some WordPress sites using the software were compromised before a fix became available for the vulnerability.

**A Directory Traversal Bug**

In a statement on its website, iThemes described the directory traversal vulnerability as impacting websites running BackupBuddy versions 8.5.8.0 through 8.7.4.1. It urged users of the plug-in to immediately update to BackupBuddy version 8.75, even if they are not currently using a vulnerable version of the plug-in.

"This vulnerability could allow an attacker to view the contents of any file on your server that can be read by your WordPress installation," the plug-in maker warned.

iThemes' alerts provided guidance on how site operators can determine if their website has been compromised and steps they can take to restore security. These measures included resetting the database password, changing their WordPress salts, and rotating API keys and other secrets in their site-configuration file.

Wordfence said it had seen attackers using the flaw to try to retrieve "sensitive files such as the /wp-config.php and /etc/passwd file which can be used to further compromise a victim."

**WordPress Plug-in Security: An Endemic Problem**

The BackupBuddy flaw is just one of thousands of flaws that have been disclosed in WordPress environments — almost all of them involving plug-ins — in recent years.

In a report earlier this year, iThemes said it identified a total of 1,628 disclosed WordPress vulnerabilities in 2021 -- and more than 97% of them impacted plug-ins. Nearly half (47.1%) were rated as being of high to critical severity. And troublingly, 23.2% of vulnerable plug-in had no known fix.

A quick scan of the National Vulnerability Database (NVD) by Dark Reading showed that several dozen vulnerabilities impacting WordPress sites have been disclosed so far in the first week of September alone.

Vulnerable plug-ins are not the only concern for WordPress sites; malicious plug-ins are another issue. A large-scale study of over 400,000 websites that researchers at the Georgia Institute of Technology conducted uncovered a staggering 47,337 malicious plug-ins installed on 24,931 websites, most of them still active.

Sounil Yu, CISO at JupiterOne, says the risks inherent in WordPress environments are like those present in any environment that leverages plug-ins, integrations, and third-party applications to extend functionality.

"As with smartphones, such third-party components extend the capabilities of the core product, but they are also problematic for security teams because they significantly increase the attack surface of the core product," he explains, adding that vetting these products is also challenging because of their sheer number and lack of clear provenance.

"Security teams have rudimentary approaches, most often giving a cursory look at what I call the three Ps: popularity, purpose, and permissions," Yu notes. "Similar to app stores managed by Apple and Google, more vetting needs to be done by the marketplaces to ensure that malicious \[plug-ins, integrations, and third-party apps\] do not create problems for their customers," he notes.

Another problem is that while WordPress is widely used, it often is managed by marketing or Web-design professionals and not IT or security professionals, says Bud Broomhead, CEO at Viakoo.

"Installing is easy and removing is an afterthought or never done," Broomhead tells Dark Reading. "Just like the attack surface has shifted to IoT/OT/ICS, threat actors aim for systems not managed by IT, especially ones that are widely used like WordPress."

Broomhead adds, "Even with WordPress issuing alerts about plug-ins being vulnerabilities, other priorities than security may delay the removal of malicious plug-ins."

Attackers Exploit Zero-Day WordPress Plug-in Vulnerability in BackupBuddy

Issue present in pingback requests feature

Issue present in pingback requests feature

  

Researchers have gone public with a six-year-old blind server-side request forgery (SSRF) vulnerability in a WordPress Core feature that could enable distributed denial-of-service (DDoS) attacks.

In a blog post published this week (September 6), Sonar researchers detailed how they were able to exploit a vulnerability in the pingback requests feature within WordPress.

The vulnerability first surfaced in 2017, yet remains unpatched.

**Pingback problem**

Pingback requests allow WordPress authors to be notified when another website links to their blog.

The pingback functionality is exposed on the XMLRPC API, which can be accessed through the file. Using this method, other blogs can announce pingbacks.

Read more of the latest news about web security vulnerabilities

This feature could enable attackers to perform DDoS attacks by maliciously asking thousands of blogs to check for pingbacks on a single victim server, Sonar researchers explained.

Although pingbacks can be turned off via a checkbox, they are still enabled by default on WordPress instances.

It’s worth noting, the researchers pointed out, that they “couldn’t generically identify ways to leverage this behavior to take over vulnerable instances without relying on other vulnerable services”.

Rather, the bug could ease the exploitation of other vulnerabilities in the affected organization’s internal network.

**Bypassing restrictions**

Thomas Chauchefoin, vulnerability researcher at Sonar and author of the blog, told The Daily Swig: “In 2012, the risks around the pingback feature started to be known, and the WordPress maintainers introduced restrictions on the destination of such requests: they would be limited to a restricted set of ports, only public IP addresses, etc.

“In essence, our finding allows getting around some of these restrictions and targeting hosts from the local network. Attackers could use it to send requests to hosts that wouldn’t have been reachable otherwise, for instance, to exploit a vulnerability in internal services.”

He added: “This bug is in the lineage of most CVEs related to pingbacks, but the oldest indicator of a researcher documenting how to get around this specific restriction is from 2017.”

DON’T MISS WordPress warning: 140k BackupBuddy installations on alert over file-read exploitation

SonarSource researchers disclosed the issue to WordPress on January 21. It was acknowledged as a duplicate bug, according to Sonar, which was reported to the WordPress team in January 2017.

Chauchefoin added: “We reported the vulnerability on January 21 through the official channels, with a pretty standard 90-day disclosure policy. After agreeing to a 30-day extension period, we reviewed a first patch still waiting to be merged upstream. Our publication occurs 228 after our initial report.”

A WordPress Security Team spokesperson told The Daily Swig: “As identified in the Sonar blog post, this is a low-impact issue and exploiting it requires ‘\[chaining\] it to additional vulnerabilities in third-party software’.

“As such, the Security Team considers the issue a low priority.”

They added: “Because of its low severity, the team is discussing whether this issue could be fixed in public as a general hardening measure.”

**Mitigation advice**

WordPress told The Daily Swig that exploiting the bug requires “vulnerabilities in multiple systems outside of WordPress”, but that it recommends website owners always use the DNS servers provided by their hosting provider.

They added: “For the pingbacks, users can turn off pingbacks. The XMLRPC endpoint will only make the HTTP requests (detailed in the Sonar blog post) if pingbacks are open for the post being pinged.

“Website owners can (a) turn off pingbacks globally using the code snippet provided in the original post and/or (b) turn off pingbacks for their blog posts.”

Chauchefoin added: “Going public with unpatched bugs is exceptional for us and was a carefully considered decision. As we had proof that our finding collided with previous public work and that it would require significant work to weaponize against real-world environments, we believe that withholding details any longer would only disadvantage defenders.

“We would like to salute the efforts of the WordPress maintainers; even if we couldn't reach the best outcome possible, backporting fixes for the software behind 40% of all websites is not trivial!”

**Previous pingback issue**

Another vulnerability in the pingback requests feature that allowed DDoS attacks was fixed by WordPress core in 2012.

The issue, reported by Acunetix, could be abused in multiple ways, researchers reported, and was fixed “as a public hardening ticket” in WordPress Core version shortly after discovery.

RECOMMENDED Vendor disputes seriousness of firewall plugin RCE flaw

Six-year-old blind SSRF vulnerability in WordPress Core feature could enable DDoS attacks

Authenticated (subscriber+) Stored Cross-Site Scripting (XSS) vulnerability in Ali Khallad's Contact Form By Mega Forms plugin <= 1.2.4 at WordPress.

*   Details
*   Reviews
*   Support
*   Development

Mega Forms is highly advanced contact form builder for WordPress, it comes with all the contact form features you will ever need, including AJAX submission, multi-page contact forms, secure file uploads, conditional logic, save and continue, and tons more. You can use Mega Forms to save time, grow customer interaction, and build better contact forms for any purpose.

Mega Forms gives you a modern interface, easy customization, and the ability to build modern & professional forms thanks to our intuitive drag & drop visual editor.

Now you can create better forms, embed them anywhere on your WordPress website, get email notification for each submission, perform custom tasks, and collect & manage data without being a coding ninja.

Mega Forms contact forms are also highly optimized for web and server performance. We know how important speed is when it comes to SEO and user experience, that’s why we have built every piece of Mega Forms with performance and usability in mind. Mega Forms will load the least possible amount of CSS & JS assets, and only store necessary data to the database to keep your website fast and provide your users with better experience.

**No Coding Skills Required**

No technical skill? No problem. You can easily design simple and complex forms with our highly advanced visual builder. Mega Forms offers a flexible row/column layout system that requires very minimal effort to build forms that blends nicely with your website design.

**Developer Friendly**

Mega Forms has been built with developers in mind. This means it’s flexible, easily extendable, and full of action and filter hooks, making it easy to customize to your own needs.

**Top Features**

Mega Forms comes with a visual editor and ton of other features:

*   Intuitive user interface
*   Drag & drop form builder
*   Optimized for speed & performance
*   Tons of free field types ( text, select, radio, checkboxes and more )
*   Regular updates & dedicated support
*   Fully responsive & mobile friendly
*   Unlimited forms & form submission
*   Merge tags support
*   Multi-steps support
*   Conditional logic support
*   Export and import forms
*   Customizable templates
*   Full control ( styles, email templates, field templates and more )
*   Developer friendly
*   Highly effective Anti-spam system ( invisible to users )

**Does Mega Forms Have A Getting Started Guide**

We’re currently still working on building Mega Forms site, once completed, it will have a complete list of resources at https://wpmegaforms.com/

**Is There A Documentation For Developers**

We’re currently still working on building Mega Forms site, once completed, it will have a complete list of resources at https://wpmegaforms.com/

**Does It Work On All Devices**

Yes, Mega Forms is completely responsive and will display forms properly on all types of devices.

**Does It Include Spam Protection**

Yes, we are using a combination of Honeypot & Timetrap to make great spambot-proof forms. We have implemented these thwarting techniques in a way that makes them very effective in detecting and blocking spam submissions without annoying the real users.

**Can I Export & Import Forms**

Yes, you can easily export and import forms via the dedicated export/import tool in the admin area.

**What Field Types Does Mega Forms Offer**

Mega Forms comes with all the fields you need:

*   Text Field
*   Paragraph Text (Textarea)
*   Dropdown Field
*   Radio Buttons
*   Checkboxes
*   Number
*   Name
*   Email Address
*   Address
*   Phone
*   Password
*   Date
*   Website
*   Hidden
*   HTML ( HTML code )
*   Divider
*   Question
*   File Upload
*   Consent

Here is a list of the field types in progress:

*   Google ReCaptacha
*   Calculated Field
*   Star Rating
*   Rangle Slider
*   Toggle
*   Signature
*   Pricing ( field group )

Here is a list of the field containers in progress:

*   Repeatable Group
*   Tabs
*   Accordions

**What Actions Does Mega Forms Offer**

Mega Forms comes with the necessary actions by default:

*   Email Notification
*   WordPress Hook

Here is a list of actions in progress:

*   Google Spreadsheet
*   Integrations ( MailChimp, ActiveCampaign, ConvertKit, AWeber, Campaign Monitor…etc )
*   Webhooks
*   Front End Posting
*   Register User

**Is It Translation Ready**

Yes, Mega Forms has full translation and localization support via the ‘megaforms’ textdomain.

**What Features Are Coming Next**

We are in the process of building more features, here is a list:

*   Form Chaining
*   Export Entries into CSV
*   Tons Of Integrations
*   Payments
*   PDF Copy
*   Save And Continue Later
*   Advanced Stats

We don’t promise all of this will be available soon, but we promise we’ll do our best to ship these features as soon as we can.

Mega Forms is a great drag n drop contact form builder. It supports all form fields you need and has a multi-page form option.

This is a very useful plugin for creating simple forms in WordPress. It saves entries in DB which can be very useful. Form builder is simple with easy to understand UI. I hope it will get more features. Ability to export entries in .xlsx and .pdf would be great.

Simple and perfect plugin to create your form

Congratulations, I'm very happy to be the second one to publish a review for this great plugin.

I think it is a useful Plugin and We wait for more Featuresز Due to the WordPress Hook, I think it is good to explain it in your Plugin Page or URL to let the Users Know how to use it.. Best regards

Read all 5 reviews

“Contact Form By Mega Forms – Drag and Drop Form Builder” is open source software. The following people have contributed to this plugin.

Contributors

*    Ali Khallad

**1.0.0**

*   First release

**1.0.1**

*   Fixed bug ( error when saving forms without adding actions )

**1.0.2**

*   Fixed bugs ( Form editior not taking full screen size, admin area styling fixes..etc )
*   Added “Section” field
*   Added “Question” field ( mainly added to help with Spam prevention )
*   Added the possibility to make “Divider” field transparent ( maily to be used as a “spacer” when needed )
*   Corrected some spelling mistakes

**1.0.3**

*   Fixed bugs
*   Added option to disable saving entries on form submission ( usefull for updating user info..etc )
*   Implemented Anti-spam technique ( Honeypot trap )
*   Added shortcode processing feature to the HTML field

**1.0.4**

*   Fixed bugs ( honeypot issues, php errors on empty form submission, choices not saving in order after moving them around…etc )
*   Added Anti-spam technique ( timetrap )

**1.0.5**

*   Fixed bugs
*   Added pre-made forms feature ( you can now create form based on pre-made templates )

**1.0.6**

*   Fixed bugs ( Styling issues, repeated name attributes when using multiple forms on same page )
*   Improvements to the overall user experience
*   Improvements to the form editor design to allow more clarity while building and managing forms
*   Added more flexibility for developers to create fields, field options..etc
*   Added AJAX submission support
*   Added conditional logic

**1.0.7**

*   Improved: order and display of options in the edit field tab ( Form editor )
*   Fixed: duplicate field setting tabs not responding ( Form editor )
*   Fixed: AJAX form doesn’t respond after first submission
*   Fixed: “Maximum call stack size exceeded” JS error when deep conditional logic is implemented
*   Added: multi-step feature ( paged forms )
*   Added: file upload field

**1.0.8**

*   Styling fixes
*   form editor preview fixes ( wrong column width + wrong description position when typed the first time )
*   Fixed: form shortcode was returning as an empty string when called via AJAX
*   Fixed: AJAX validation was adding duplicate notices for choice fields (radios, checkboxes)
*   Fixed: bug in mfget_option function that mixes between false and non-existing setting values causing some of the true/false settings to have unexpected behavior
*   Added: Save and continue feature
*   Added: Consent field

**1.0.9**

*   Extended “One line text” and “Paragraph text” fields so that the user can view number of characters typed if the maximum length is set for these fields.
*   Added the ability to control field label visibility (show/hide)
*   Fixed bug: When duplicating a field in the form editor, the field values were not copied over to the new field
*   Fixed bug: When adding field tag in the form editor, the field preview didn’t update with the new field value because the change event is not triggered for that field

**1.1.0**

*   Fixed: emails were not being sent when there are multiple recipients

**1.1.1**

*   Performance optimization ( combined and minifed CSS & JS resources )
*   Improved conditional logic

**1.1.2**

*   Fix: a JS bug that prevents items from displaying in the single entry page
*   Fix: email header issues
*   Fix: conditional logic not working on compound fields
*   Improvement: Make phone & number fields display a keypad on mobile view instead of the default keyboard.

**1.1.3**

*   Update: include all PRO features in free version and drop the paid version ( Mega Forms with all PRO features is now free ).
*   Fix: a bug in the referrer column in entries table that prevents the creation of entries if the referrer is longer than 100 chars.

**1.1.4**

*   added filter hook “mf\_bypass\_session\_error” to allow bypassing session validation error ( usefull when cookies aren’t allowed/saved ).

**1.1.5**

*   Fix: form email action issues ( subject was empty by default, email not sending when the “from” field is not formatted correctly )
*   Fix: entries list display ( the list was showing all columns/fields by default which can cause unpleasant view for large forms)
*   Fix: fields order was based on ID order on different areas ( emails, entries, entry lists..etc ), this is corrected to show fields in the same order as they appear on the form.
*   Improved the “Change columns visibility” option design/display on the entries list page
*   Ensure that once an entry is deleted, all associated files will be deleted as well.
*   Added a link to download/view uploaded files in email notifications

**1.1.6**

*   Fix: bug in file field description ( removing file field description was not possible )
*   Added WordPress shortcodes support to the “default value” field
*   Fix: syntax error during activation

**1.1.7**

*   Added cookies compatibility with wpengine ( to prevent caching issues )
*   Fixed a bug with WP admin notices ( hiding notices outside the plugin’s pages )
*   Fixed a bug with the plugin’s admin snackbar ( not being loaded on some pages )

**1.1.8**

*   Bug fixes in the drag and drop uploads field ( inaccurate file count … )

**1.1.9**

*   Fix: a bug in “more options” selection in email action that only allows a single value to be saved
*   Fix: a bug making the filetype case-sensitive in upload field

**1.2.0**

*   Fix: a bug in checkbox option that is causing only the last selected value to be saved from a checkbox list in AJAX submissions
*   Fix: a bug in “form save” process that is causing only a single “form action” to be saved.

**1.2.1**

*   Fix: maintain the selected tab selected after page refresh ( admin settings )
*   Added: ability to export form entries

**1.2.2**

*   Changed Mega Forms session cookie prefix from “mf” to “wordpress\_mf” to ensure compatibility with caching plugins and hosting providers caching.
*   Fixed: CSS clearfix incompatibility with some theme which causing the layout of some fields to break ( eg; address field when error are displayed )
*   Fixed: Bug that prevented the “CSS Classes” value from being saved for form fields.

**1.2.3**

*   Styling fixes
*   Reduced resources ( CSS, JS ) size.

**1.2.4**

*   Add support to multisite

**1.2.5**

*   CSS Fixes
*   Fixed a XSS issue. Credit: ptsfence.

CVE-2022-40191: Contact Form By Mega Forms – Drag and Drop Form Builder

Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team wpForo Forum plugin <= 2.0.5 at WordPress.

CVE-2022-38144: wpForo Forum

Authenticated (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Apasionados Export Post Info plugin <= 1.1.0 at WordPress.

*   Details
*   Reviews
*   Installation
*   Support
*   Development

**Description**

This plugin exports posts Date published, Post title, Word Count, Status, URL and Category to a CSV file, allowing to have an overview of the topics and titles published in the blog.

We created this plugin because we generate large amounts of content for blogs and we often need to lookup the topics that were already covered before in a blog. As we don’t want to export the titles by hand we developed this plugin.

**What can I do with this plugin?**

This plugin exports posts Date published, Post title, Word Count, Status, URL and Category to a CSV file that can be imported into Excel.

**What ideas is this plugin based on?**

We were searching for a plugin that allowed us to export the post titles and found Export All URLs. Unfortunately the plugin didn’t export the publish date, status and word count, so we decided to create a new plugin with this information and the the ability to translate it.

**System requirements**

PHP version 5.5 or greater.

**Export Post Info to CSV Plugin in your Language!**

This first release is avaliable in English and Spanish. In the “languages” folder we have included the necessarry files to translate this plugin.

If you would like the plugin in your language and you’re good at translating, please drop us a line at Contact us.

**Further Reading**

You can access the description of the plugin in Spanish at: Export Post Info to CSV en español.

**Contact**

For further information please send us an email.

**Translating WordPress Plugins**

The steps involved in translating a plugin are:

1.  Run a tool over the code to produce a POT file (Portable Object Template), simply a list of all localizable text. Our plugins allready havae this POT file in the /languages/ folder.
2.  Use a plain text editor or a special localization tool to generate a translation for each piece of text. This produces a PO file (Portable Object). The only difference between a POT and PO file is that the PO file contains translations.
3.  Compile the PO file to produce a MO file (Machine Object), which can then be used in the theme or plugin.

In order to translate a plugin you will need a special software tool like poEdit, which is a cross-platform graphical tool that is available for Windows, Linux, and Mac OS X.

The naming of your PO and MO files is very important and must match the desired locale. The naming convention is: language_COUNTRY.po and plugins have an additional naming convention whereby the plugin name is added to the filename: pluginname-fr_FR.po

That is, the plugin name name must be the language code followed by an underscore, followed by a code for the country (in uppercase). If the encoding of the file is not UTF-8 then the encoding must be specified.

For example:

*   en\_US � US English
*   en\_UK � UK English
*   es\_ES � Spanish from Spain
*   fr\_FR � French from France
*   zh\_CN � Simplified Chinese

A list of language codes can be found here, and country codes can be found here. A full list of encoding names can also be found at IANA.

**Screenshots**

**Installation**

1.  First you will have to upload the plugin to the /wp-content/plugins/ folder.
2.  Then activate the plugin in the plugin panel.
3.  Go to SETTINGS / EXPORT POST INFO.
4.  Save a random string to make it harder for somebody to access your exported data.
5.  Download your CSV file.

**FAQ**

**Why did you make this plugin?**

We couldn’t find a plugin that would give us the functionality we were looking for:  
1) Export publish date.  
2) Export word count.  
3) Easy translation of the plugin into other languages. So far English and Spanish translations are included.

**Why do I have to setup a random string for the name of the export CSV file?**

Other plugins always export the file with the same name and in the same folder so it’s easy to access this file. We don’t want that this file can be easily found, so we decided to let you setup a random string to make the file name harder to guess.

**Does Export Post Info make changes to the database?**

Yes. It created an entry in the options table where the random string is stored.

**How can I check out if the plugin works for me?**

Install and activate. Go to settings / Export Post Info. Save random string. And download CSV file.

**How can I remove Export Post Info to CSV?**

You can simply activate, deactivate or delete it in your plugin management section.

**Which PHP version do I need?**

This plugin has been tested and works with PHP versions 5.5 and greater. WordPress itself recommends using PHP version 7.3 or greater. If you’re using a PHP version lower than 5.5 please upgrade your PHP version or contact your Server administrator.

**Are there any known incompatibilities?**

Yes. On a multi-language site the export will not work correctly.

**Is this plugin compatible with WPML**

Yes, but only the posts of the main language are exported. Post in secondary languages are not exported at this moment. We are working on this because we would like to have this feature but for us it isn’t easy to code.

**Are there any server requirements?**

Yes. The plugin requires a PHP version 5.5 or higher and we recommend using PHP version 7.3 or higher.

**Do you make use of Export Post Info to CSV yourself?**

Of course we do. That’s why we created it. 😉

**Reviews**

From uploading the plugin to downloading the CSV file took about 15 seconds! Just perfect - thank you!

This plugin exported exactly what I needed, and it did it quickly and painlessly. Thanks very much to the devs!

Time saver, works just fine

Super plugin, très simple à utiliser. Merci !

Thank you so much for this amazing little plugin that did exactly what I needed. Saved me hours of work in creating a spreadsheet with all my posts so I can create an optimization checklist. The other popular export all posts plugin only exports the post title, url and category. Without the date and other fields, I would have to go in and manually add that data. Export Post Info (this plugin) did all of it perfectly. Keep up the great work!

October 11, 2018

Not sure why this plug in has no reviews. Did for me EXACTLY what I needed even though it is two years old. Muchas Gracias

Read all 6 reviews

**Contributors & Developers**

“Export Post Info” is open source software. The following people have contributed to this plugin.

Contributors

*    apasionados

**Changelog****1.2.0 (06/Sep/2022)**

*   Security update: Please update your plugin. We escaped data to increase your security.
*   Corrected PHP notices when debug was active.

**1.1.0 (25/Aug/2019)**

*   Now posts with status published, future and private are exported. Until now only posts with status published were exported.
*   Added post status column to the export file.
*   PHP version must be 5.6 or higher. Recommended PHP version: 7.3.

**1.0.4 (08/Abr/2017)**

*   Cleaned up code + Changed functions name to be unique and avoid conflicts with other plugins or themes.

**1.0.3 (07/Abr/2017)**

*   Added check for PHP version when activating the plugin. PHP version must be 5.5 o greater.

**1.0.2 (07/Abr/2017)**

*   Solved error in Word Count with words containing UTF-8 characters.

**1.0.1 (07/Abr/2017)**

*   Word count would not count all words of a post if a tag was present.

**1.0.0 (07/Abr/2017)**

*   First official release.

CVE-2022-38068: Export Post Info

Cross-Site Request Forgery (CSRF) vulnerability in Alexey Trofimov's Access Code Feeder plugin <= 1.0.3 at WordPress.

CVE-2022-38059

Privilege Escalation (subscriber+) vulnerability in Pop-up plugin <= 1.1.5 at WordPress.

CVE-2022-38070

Unauthenticated Plugin Settings Change & Data Deletion vulnerabilities in WP Shop plugin <= 3.9.6 at WordPress.

*   Details
*   Reviews
*   Support
*   Development

This plugin has been closed as of September 5, 2022 and is not available for download. This closure is temporary, pending a full review.

Являюсь обладателем , который по глупости и началу знакомства с wordpress купил две темы для своих интернет магазинов у WP Shop о чем сейчас жалею . 1) Плагин WP Shop работает только с темами WP Shop и если вы захотите перевести свой сайт на тему других создателей - у вас не получится или получится полный .... 2) Очень важно !!! - Плагин не обновляют он работает на версии максимально PHP 7.0 и то обновили после моих долгих просьб ( на момент написания отзыва уже как пол года существует версия PHP 7.4 ) Если вы переведете на новую версию PHP - сайт - ЛОЖИТСЯ ! 3) Хотел выбросить темы от WP Shop и перейти на темы других создателей с WooCommerce но жалко терять рейтинг страниц сайта . Но думаю придётся сделать новый сайт на WooCommerce и делать редирект всех товаров с тем сайтов от WP Shop на новый от WooCommerce 4) Не повторяйте моих ошибок покупайте сразу современные темы с работой в WooCommerce , которые со временем легко можно - заменить и они еще дешевле вам обойдутся чем старые темы от WP Shop 5) 100% уверен что хорошие отзывы о плагине писали сами WP Shop

Ни в коем случае не связывайтесь с этими разработчиками и ничего у них не покупайте. Тот функционал, который они обещают в про версии – обман. Они просто возьмут с вас деньги, а потом от всего откажутся, в том числе от поддержки. Просто посмотрите их кривой сайт и полуживую документацию и сами всё поймёте!

На мой взгляд, лучший модуль интернет-магазина для сайта на русском языке. Есть все необходимое для продажи большинства товаров, включая виртуальные (цифровые). Грамотная оперативная поддержка в группе ВКонтакте. Спасибо разработчикам за их труд!

It works correctly only with there onw Themes

Перепробовал 4 плагина интернет магазина для ВП, ни чего подходящее WP-Shop не нашел. Все на русском, ни чего переводить не надо, легко синхронизировать с 1С, волшебная функция Экспорт импорт, и куча других плюсов. Спокойно можно разобраться в течение часа как все работает не имея специального образования.

Отличный плагин, постоянно пользуюсь. Тут есть все для настройки простого и надежного интернет магазина.

Read all 16 reviews

“WP Shop” is open source software. The following people have contributed to this plugin.

Contributors

CVE-2022-36793: WP Shop

Rating increase/decrease via race condition in Lester 'GaMerZ' Chan WP-PostRatings plugin <= 1.89 at WordPress.

Tag

#wordpress