CVE-2013-5725
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file...
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file actions, which allows remote attackers to overwrite arbitrary files via the name and text parameters in a byword://replace URL.
Exploit likelihood
What each source reports
NVD Score used
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file actions, which allows remote attackers to overwrite arbitrary files via the name and text parameters in a byword://replace URL.
- Record
CVE-2013-5725- CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:N/I:P/A:N - Weakness
- CWE-264
- Updated
- 2026-11-02
CVE List No score
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file actions, which allows remote attackers to overwrite arbitrary files via the name and text parameters in a byword://replace URL.
- Record
CVE-2013-5725- Updated
- 2026-11-02
EUVDEUVD-2013-5562 No score
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file actions, which allows remote attackers to overwrite arbitrary files via the name and text parameters in a byword://replace URL.
- Record
EUVD-2013-5562- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-qh36-5vfv-6xmm No score
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file...
The Metaclassy Byword app 2.x before 2.1 for iOS does not require confirmation of Replace file actions, which allows remote attackers to overwrite arbitrary files via the name and text parameters in a byword://replace URL.
- Record
GHSA-qh36-5vfv-6xmm- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2013-5725 is a medium vulnerability (CVSS 5.0) in Metaclassy Byword, published October 1, 2013. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.07%, the 65th percentile. No source names a fixed version.