`@Ҡ d Z ddlZddlZddlmZ ddlmZmZmZm Z ddl mZmZ ddl mZmZ ddlmZ ddlmZ G d d e Zdeded efdZdeded efdZdeded efdZdeded efdZded efdZ d)dedededz dedz dedz dedz dedz dedz dedz dedz dedz fd Zd!ee d ee fd"Zd#efd$Z ded efd%Z!d&edz d efd'Z"d edz fd(Z#dS )*a0 Helper functions for WordPress CVE protection incidents. WordPress incidents are stored in a dedicated wordpress_incident table with plugin-specific data stored in the extra_info JSON field. This module provides helper functions to work with WordPress incidents. Available for both AV and IM360 modes. N) timedelta) CharField FloatFieldIntegerField TextField) JSONFieldfn)Modelinstance)apply_order_by)OrderByc R e Zd ZdZ edd Z ed Z ed Z e d Z ed Z ed Z ed Z ed Z ed Z edd Z edd Z ed Z G d d ZdS )WordpressIncidentz WordPress incident model for CVE protection. Uses dedicated wordpress_incident table created in migration 191. Unique constraint on (abuser, name, plugin, rule, severity, domain) allows deduplication similar to the aggregate plugin. T)primary_keynull)r country_id)r column_nameN)r defaultc $ e Zd Zej ZdZdZdS )WordpressIncident.Metawordpress_incident)))abusernamepluginruleseveritydomainTN)__name__ __module____qualname__r dbdatabasedb_tableindexes ]/opt/imunify360/venv/lib/python3.11/site-packages/defence360agent/model/wordpress_incident.pyMetar 1 s! ;' r&