Unauthorized synchronization via missing nonce validation
Published Sep 27, 2025 · Updated Sep 27, 2025
Cross-site request forgery in Sync Feedly 1.0.1 and earlier allows remote attackers to trigger Feedly content synchronization. The crsf_cron_job_func function processes synchronization requests without validating a WordPress nonce. Exploitation requires a site administrator to act on a forged request; the result is an unauthorized synchronization run, with post creation dependent on available Feedly content.
Summary
What happened
Cross-site request forgery in Sync Feedly 1.0.1 and earlier allows remote attackers to trigger Feedly content synchronization. The crsf_cron_job_func function processes synchronization requests without validating a WordPress nonce. Exploitation requires a site administrator to act on a forged request; the result is an unauthorized synchronization run, with post creation dependent on available Feedly content.
The record
- CVE
- CVE-2025-9894
- Published
- Sep 27, 2025
- Updated
- Sep 27, 2025
- Vendor
- cristianr909090
- Product
- Sync Feedly
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2025CVE publishedPublication date reported by the CVE source.
- Sep 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo