Seriously Simple Podcasting < 3.0.0 - Unauthenticated Administrator Email Disclosure
Noroxi assessment
Priority: Monitor (action score 22/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Unknown Seriously Simple Podcasting 3.0.0.
Low priority for now. Upgrade to Unknown Seriously Simple Podcasting 3.0.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Seriously Simple Podcasting WordPress plugin before 3.0.0 discloses the Podcast owner's email address (which by default is the admin email address) via an unauthenticated crafted request.
- Published
- Mar 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-201
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| castos | seriously simple podcasting | cpe:2.3:a:castos:seriously_simple_podcasting |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- castos seriously simple podcastingbefore 3.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
Unknown Seriously Simple Podcasting
- before 3.0.0affected · semver
Same product
castos: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-9667Seriously Simple Podcasting <= 3.5.0 - Reflected Cross-Site Scripting via add_query_arg Parameter24Monitor
- CVE-2024-25599WordPress Seriously Simple Podcasting plugin <= 3.0.2 - Reflected Cross Site Scripting (XSS) vulnerability24Monitor
- CVE-2025-49923WordPress Seriously Simple Podcasting plugin <= 3.11.1 - Cross Site Scripting (XSS) vulnerability23Monitor
- CVE-2025-66060WordPress Seriously Simple Podcasting plugin <= 3.13.0 - Broken Access Control vulnerability21Monitor
- CVE-2025-66059WordPress Seriously Simple Podcasting plugin <= 3.13.0 - Sensitive Data Exposure vulnerability21Monitor
- CVE-2022-4571Seriously Simple Podcasting < 2.19.1 - Contributor+ Stored XSS21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Unknown Seriously Simple Podcasting | 3.0.0 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2023-6444 | — |
| Proof-of-concept repository on GitHub | stars:0 | 2024-08-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+148 d
- TodayOct 17, 2026+950 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- WPScancoordinator
- Krzysztof Zając (CERT PL)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →