Wp Subtitle
Approved changes feed: RSS · Atom
cpe:2.3:a:wp_subtitle_project:wp_subtitle:*:*:*:*:*:wordpress:*:*part: a version: * update: *
| Vendor | Wp Subtitle Project (54907cbc-6dcb-54c9-9bf5-1865989c2d61) |
|---|---|
| Product | Wp Subtitle (15733327-b3fa-54a6-911b-e9ad60c4e47c) |
| 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-2022-1393 |
vulnerable | 2026-06-08 05:39:13.100078 |
WP Subtitle < 3.4.1 - Contributor+ Stored Cross-Site Scripting
The WP Subtitle WordPress plugin before 3.4.1 adds a subtitle field and provides a shortcode to display it via [wp_subtitle]. The subtitle is stored as a custom post meta with the key: "wps_subtitle", which is sanitized upon post save/update, however is not sanitized when updating it directly from the post meta update button (via AJAX) - and this makes the XSS exploitable by authenticated users with a role as low as contributor.
Published: 2022-05-16T14:30:51.000Z
Updated: 2024-08-03T00:03:06.053Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.