Power Up For Autoptimize
Approved changes feed: RSS · Atom
cpe:2.3:a:rapidload:power-up_for_autoptimize:*:*:*:*:*:wordpress:*:*
part: a version: * update: *
| Vendor | Rapidload (57598163-7bea-5fcb-a5ab-c2f76eeffb6c) |
|---|---|
| Product | Power Up For Autoptimize (eeb02dde-c04b-5b12-b170-6c43b8e54064) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-31288 |
vulnerable | 2026-06-08 06:35:31.244181 |
WordPress RapidLoad plugin <= 2.2.11 - Server Side Request Forgery (SSRF) vulnerability
HIGH (7.2)
Server-Side Request Forgery (SSRF) vulnerability in RapidLoad RapidLoad Power-Up for Autoptimize.This issue affects RapidLoad Power-Up for Autoptimize: from n/a through 2.2.11.
Published: 2024-04-07T17:18:47.447Z
Updated: 2026-04-28T16:09:30.211Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1346 |
vulnerable | 2026-06-08 05:52:35.677234 |
RapidLoad Power-Up for Autoptimize <= 1.7.1 - Cross-Site Request Forgery via 'clear_page_cache'
MEDIUM (4.3)
The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.1. This is due to missing or incorrect nonce validation on the clear_page_cache function. This makes it possible for unauthenticated attackers to clear the plugin's cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2023-03-10T19:07:39.988Z
Updated: 2026-04-08T17:16:23.799Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1345 |
vulnerable | 2026-06-08 05:52:35.676858 |
RapidLoad Power-Up for Autoptimize <= 1.7.1 - Cross-Site Request Forgery via 'queue_posts'
MEDIUM (4.3)
The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.1. This is due to missing or incorrect nonce validation on the queue_posts function. This makes it possible for unauthenticated attackers to modify the plugin's cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2023-03-10T19:07:23.931Z
Updated: 2026-04-08T17:25:09.999Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1344 |
vulnerable | 2026-06-08 05:52:35.676240 |
RapidLoad Power-Up for Autoptimize <= 1.7.1 - Cross-Site Request Forgery via 'uucss_update_rule'
MEDIUM (4.3)
The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.1. This is due to missing or incorrect nonce validation on the uucss_update_rule function. This makes it possible for unauthenticated attackers to modify the plugin's cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2023-03-10T19:07:04.653Z
Updated: 2026-04-08T16:42:38.683Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1343 |
vulnerable | 2026-06-08 05:52:35.672115 |
RapidLoad Power-Up for Autoptimize <= 1.7.1 - Cross-Site Request Forgery via 'attach_rule'
MEDIUM (4.3)
The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.1. This is due to missing or incorrect nonce validation on the attach_rule function. This makes it possible for unauthenticated attackers to modify the plugin's cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2023-03-10T19:06:46.944Z
Updated: 2026-04-08T16:36:19.912Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1342 |
vulnerable | 2026-06-08 05:52:35.671658 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1341 |
vulnerable | 2026-06-08 05:52:35.671226 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1340 |
vulnerable | 2026-06-08 05:52:35.670769 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1339 |
vulnerable | 2026-06-08 05:52:35.670211 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1338 |
vulnerable | 2026-06-08 05:52:35.669686 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1337 |
vulnerable | 2026-06-08 05:52:35.669161 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1336 |
vulnerable | 2026-06-08 05:52:35.668789 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1335 |
vulnerable | 2026-06-08 05:52:35.668407 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1334 |
vulnerable | 2026-06-08 05:52:35.667811 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1333 |
vulnerable | 2026-06-08 05:52:35.666355 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.