CVE-2005-10002: A vulnerability, which was classified as critical, was found in almosteffortless secure-files Plugin up to 1.1

Q: How do I fix CVE-2005-10002?

secure files: upgrade to 1.2. Exact commands for each OS are on this page.

Q: Is CVE-2005-10002 being exploited?

CVE-2005-10002 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2005-10002 affect?

CVE-2005-10002 affects secure files. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in almosteffortless secure-files Plugin up to 1.1 on WordPress. Affected is the function sf_downloads of the file secure-files.php. The manipulation of the argument downloadfile l

Q: How urgent is CVE-2005-10002?

Priority 34/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2005-10002 is a medium-severity flaw (CVSS 5.5) affecting secure files. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as critical, was found in almosteffortless secure-files Plugin up to 1.1 on WordPress. Affected is the function sf_downloads of the file secure-files.php. The manipulation of the argument downloadfile leads to path traversal. Upgrading to version 1.2 is able to address this issue. The name of the patch is cab025e5fc2bcdad8032d833ebc38e6bd2a13c92. It is recommended to upgrade the affected component. The identi

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-22
Published	2023-10-29
Last modified	2026-06-16

Publisher (CNA): VulDB · Vendor: wp-plugins

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-10-29 15:15 UTCPublished CVE record published
2026-06-16 22:12 UTCUpdated Record last modified

wp-plugins secure files UPGRADE

Affected: < 1.2

Fixed in: 1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy secure-files || rpm -q secure-files || secure-files --version

2. UPGRADE to 1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade secure-files

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade secure-files

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-10002?

secure files: upgrade to 1.2. Exact commands for each OS are on this page.

Is CVE-2005-10002 being exploited?

CVE-2005-10002 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-10002 affect?

CVE-2005-10002 affects secure files. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in almosteffortless secure-files Plugin up to 1.1 on WordPress. Affected is the function sf_downloads of the file secure-files.php. The manipulation of the argument downloadfile l

How urgent is CVE-2005-10002?

Priority 34/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs