Tiempo.com <= 0.1.2 - Stored XSS via CSRF
Priority LOW 27Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
Summary
The Tiempo.com WordPress plugin through 0.1.2 does not have CSRF check when creating and editing its shortcode, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack
Why it matters now
EPSS 0.00237 14th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA and NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Tiempo.com | up to 0.1.2 | — | No fix listed | CNA |
- Tiempo.com VendorUnknown Affected up to 0.1.2 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2023-0058
- 2026-10-03 Alias added: GHSA-m256-5rj4-75c4
References
More Tiempo vulnerabilities
- TI-2023-02131 Tiempo.com <= 0.1.2 - Reflected XSS CVSS 3.1MEDIUM 6.1
- TI-2023-02130 Tiempo.com <= 0.1.2 - Shortcode Deletion via CSRF CVSS 3.1MEDIUM 4.3
Sources
- CVE-2023-0058 · CVE Program
- CVE-2023-0058 · NVD
- FIRST EPSS
- GHSA-m256-5rj4-75c4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences